Draft: changes for adding gitlab_secret_manager in CI pipeline
What does this MR do and why?
Adding gitlab_secret_manager to the CI pipeline
Sample gitlab-ci.yml file
test_openbao_direct:
id_tokens:
GITLAB_ID_TOKEN:
aud: secrets.gitlab.com
secrets:
TEST_SECRET:
gitlab_secret_manager:
name: foo # translates to secret `kv-v2/data/projects/53/foo`, field `val`
token: $GITLAB_ID_TOKEN
script:
- echo "testing Openbao in CI"
- cat $TEST_SECRET
- echo "done."
Before executing the pipeline, make sure the Openbao is running and a secret is saved inside openbao using the following steps #461677 (comment 1918666032). Update the project id to your local project id. Thanks
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Edited by Shabini Rajadas