diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-03 03:09:13 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-03 03:09:13 +0300 |
| commit | 7cf5520071ef2f89a96167a60ce0693bd694fad3 (patch) | |
| tree | 67a8a1513d908ddb02c2d903add040a2e49d009b /doc | |
| parent | fecb8ece925c48cf64969f1ecced12e4c4497706 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/development/database/loose_foreign_keys.md | 6 | ||||
| -rw-r--r-- | doc/development/database/understanding_explain_plans.md | 1 | ||||
| -rw-r--r-- | doc/user/clusters/agent/user_access.md | 2 |
3 files changed, 6 insertions, 3 deletions
diff --git a/doc/development/database/loose_foreign_keys.md b/doc/development/database/loose_foreign_keys.md index fd380bee385..08d618a26ae 100644 --- a/doc/development/database/loose_foreign_keys.md +++ b/doc/development/database/loose_foreign_keys.md @@ -251,8 +251,12 @@ When the loose foreign key definition is no longer needed (parent table is remov we need to remove the definition from the YAML file and ensure that we don't leave pending deleted records in the database. -1. Remove the deletion tracking trigger from the parent table (if the parent table is still there). 1. Remove the loose foreign key definition from the configuration (`config/gitlab_loose_foreign_keys.yml`). + +The deletion tracking trigger needs to be removed only when the parent table no longer uses loose foreign keys. +If the model still has at least one `loose_foreign_key` definition remaining, then these steps can be skipped: + +1. Remove the trigger from the parent table (if the parent table is still there). 1. Remove leftover deleted records from the `loose_foreign_keys_deleted_records` table. Migration for removing the trigger: diff --git a/doc/development/database/understanding_explain_plans.md b/doc/development/database/understanding_explain_plans.md index 92688eb01dc..3e8978e1046 100644 --- a/doc/development/database/understanding_explain_plans.md +++ b/doc/development/database/understanding_explain_plans.md @@ -352,7 +352,6 @@ Indexes: "index_users_on_static_object_token" UNIQUE, btree (static_object_token) "index_users_on_unlock_token" UNIQUE, btree (unlock_token) "index_on_users_name_lower" btree (lower(name::text)) - "index_users_on_accepted_term_id" btree (accepted_term_id) "index_users_on_admin" btree (admin) "index_users_on_created_at" btree (created_at) "index_users_on_email_trigram" gin (email gin_trgm_ops) diff --git a/doc/user/clusters/agent/user_access.md b/doc/user/clusters/agent/user_access.md index a1e98a2db76..b3735770a97 100644 --- a/doc/user/clusters/agent/user_access.md +++ b/doc/user/clusters/agent/user_access.md @@ -202,7 +202,7 @@ glab cluster agent update-kubeconfig --agent '<agent-id>' --kubeconfig ~/gitlab. ### Configure local access manually using a personal access token -You can configure access to a Kubernetes cluster using a long-lived personal access token following these steps: +You can configure access to a Kubernetes cluster using a long-lived personal access token: 1. On the left sidebar, select **Search or go to** and find your project. 1. Select **Operate > Kubernetes clusters** and retrieve the numerical ID of the agent you want to access. You need the ID to construct the full API token. |