-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
terraform: provision prow-related secrets via terraform #2845
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
Embedded the secret data in a second locals block to avoid merge conflict with other PRs in flight
b5b00b8
to
3571c88
Compare
/lgtm |
/hold |
/hold cancel |
/hold |
/hold cancel |
Deployed for k8s-infra-prow-build-trusted #!/usr/bin/env bash
set -eu
secrets=(
cncf-ci-github-token
k8s-infra-kops-e2e-tests-aws-ssh-key
k8s-triage-robot-github-token
snyk-token
)
project=k8s-infra-prow-build-trusted
for secret in "${secrets[@]}"; do
terraform import \
"google_secret_manager_secret.build_cluster_secrets[\"${secret}\"]" \
"projects/${project}/secrets/${secret}"
done
terraform apply |
Deployed for k8s-infra-prow-build via |
Related:
This moves management of k8s-infra-prow-build-trusted's secrets to terraform
Then follows a similar pattern to setup secrets for k8s-infra-prow-build that will be populated and hooked up to ExternalSecret CRDs as followup
This was written with separate locals blocks to avoid merge conflicts with outstanding terraform PRs for prow