Support loading secrets directly into services
Managed Cloud Run now has support for loading secrets into environment variables and files.
Extend this module to support loading secrets.
Designs
- Show closed items
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Dr Rich Wareham changed milestone to %DevOps Sprint 122
changed milestone to %DevOps Sprint 122
- Dr Rich Wareham added 1 deleted label
added 1 deleted label
- Dr Abraham Martin added priority2 Medium label
added priority2 Medium label
- Dr Abraham Martin added Operations label
added Operations label
- Dr Abraham Martin added to epic uis/devops&25
added to epic uis/devops&25
- Dr Abraham Martin changed time estimate to 1d 4h
changed time estimate to 1d 4h
- Dr Abraham Martin added workflowSprint Ready label and removed 1 deleted label
added workflowSprint Ready label and removed 1 deleted label
- Dr Abraham Martin set weight to 2
set weight to 2
- Dr Abraham Martin changed milestone to %DevOps Sprint 124
changed milestone to %DevOps Sprint 124
- Dr Abraham Martin changed milestone to %DevOps Sprint 122
changed milestone to %DevOps Sprint 122
- Dr Abraham Martin assigned to @ap2261
assigned to @ap2261
- Contributor
The Terraform module
google_cloud_run_service
now supports direct reference to the secrets in SM as env vars or files. Determine what needs to be mounted where.
Supports volumes
volumes { name = "a-volume" secret { secret_name = google_secret_manager_secret.secret.secret_id items { key = "1" path = "my-secret" } } }
env { name = "SECRET_ENV_VAR" value_from { secret_key_ref { name = google_secret_manager_secret.secret.secret_id key = "1" }
- Contributor
Yes, indeed. In my case, I'm configuring Cloud Run service via the module "gcp-cloud-run-app" which doesn't yet support this extension.
- Arun Patel added workflowIn Progress label and removed workflowSprint Ready label
added workflowIn Progress label and removed workflowSprint Ready label
- Contributor
I ran into an "obfuscated" error message:
Details: [ { "@type": "type.googleapis.com/google.rpc.BadRequest", "fieldViolations": [ { "description": "spec.template.spec.containers[0].volumeMounts should be empty", "field": "spec.template.spec.containers[0].volumeMounts" } ] } ]
Which turned out to be a bug in the docs (from the links above):
metadata { annotations = { generated-by = "magic-modules" "run.googleapis.com/launch-stage" = "ALPHA" } }
Should be
BETA
. And if you have already appliedALPHA
, remove any lifecyle rule, probablyrm -rf .terraform/
and re-apply. Collapse replies - Author Owner
- Arun Patel mentioned in merge request !25 (merged)
mentioned in merge request !25 (merged)