diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-28 18:08:03 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-06-28 18:08:03 +0300 |
| commit | 59469a17821eda8a34d08b1e46584e902d1e963a (patch) | |
| tree | 504eb7237ea7cadb589e0791fa243f7bf93237a7 /doc/ci/environments | |
| parent | e2b92514e3def8074c0855100632ebb9935d2a19 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/environments')
| -rw-r--r-- | doc/ci/environments/deployment_safety.md | 2 | ||||
| -rw-r--r-- | doc/ci/environments/index.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md index c57dc99f341..46141e2426b 100644 --- a/doc/ci/environments/deployment_safety.md +++ b/doc/ci/environments/deployment_safety.md @@ -110,7 +110,7 @@ for an explanation of these roles and the permissions of each. Production secrets are needed to deploy successfully. For example, when deploying to the cloud, cloud providers require these secrets to connect to their services. In the project settings, you can -define and protect CI/CD variables for these secrets. [Protected variables](../variables/README.md#protect-a-cicd-variable) +define and protect CI/CD variables for these secrets. [Protected variables](../variables/index.md#protect-a-cicd-variable) are only passed to pipelines running on [protected branches](../../user/project/protected_branches.md) or [protected tags](../../user/project/protected_tags.md). The other pipelines don't get the protected variable. You can also diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md index 62c58302886..c9b5690ea41 100644 --- a/doc/ci/environments/index.md +++ b/doc/ci/environments/index.md @@ -691,7 +691,7 @@ with `review/` would have that variable available. Some GitLab features can behave differently for each environment. For example, you can -[create a project CI/CD variable to be injected only into a production environment](../variables/README.md#limit-the-environment-scope-of-a-cicd-variable). +[create a project CI/CD variable to be injected only into a production environment](../variables/index.md#limit-the-environment-scope-of-a-cicd-variable). In most cases, these features use the _environment specs_ mechanism, which offers an efficient way to implement scoping in each environment group. |