Commit f9d2dd75 authored by Suzanne Selhorn's avatar Suzanne Selhorn

Merge branch 'group-env-vault' into 'master'

Update secrets docs to point to Vault

See merge request gitlab-org/gitlab!33395
parents 6dfdecb0 38b6df00
...@@ -404,9 +404,8 @@ script: ...@@ -404,9 +404,8 @@ script:
You can define per-project or per-group variables You can define per-project or per-group variables
that are set in the pipeline environment. Group-level variables are stored out of that are set in the pipeline environment. Group-level variables are stored out of
the repository (not in `.gitlab-ci.yml`) and are securely passed to GitLab Runner the repository (not in `.gitlab-ci.yml`) and are securely passed to GitLab Runner,
making them available during a pipeline run. It's the **recommended method** to which makes them available during a pipeline run. For Premium users who do **not** use an external key store or who use GitLab's [integration with HashiCorp Vault](../examples/authenticating-with-hashicorp-vault/index.md), we recommend using group environment variables to store secrets like passwords, SSH keys, and credentials.
use for storing things like passwords, SSH keys, and credentials.
Group-level variables can be added by: Group-level variables can be added by:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment