Skip to content

Allow oac-prod-infra to read an additional secret - #62

Merged
naved001 merged 1 commit into
CCI-MOC:mainfrom
naved001:oac-prod-infra/b2-secret
Oct 27, 2026
Merged

naved001 merged 1 commit into
CCI-MOC:mainfrom
naved001:oac-prod-infra/b2-secret

Conversation

@naved001

Copy link
Copy Markdown
Contributor

This secret is necessary so that the cronjobs on oac-prod-infra can write metrics for oac-prod-workload0 to the b2 bucket.

This secret is necessary so that the cronjobs on oac-prod-infra can
write metrics for oac-prod-workload0 to the b2 bucket.
@naved001
naved001 force-pushed the oac-prod-infra/b2-secret branch from f5695a8 to d73ac52 Compare October 27, 2026 14:51
@naved001 naved001 changed the title Allow oac-prod-infra to read b2 an additional secret Allow oac-prod-infra to read an additional secret Oct 27, 2026
Comment thread main.tf
oidc_bucket_domain_name = aws_s3_bucket.oac_oidc.bucket_regional_domain_name
cert_manager_policy_arn = module.cert_manager_policy["cert_manager_policy_oac_prod_infra"].policy_arn
eso_readable_secret_prefixes = [
"b2-key/oac-prod-workload0-rw",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nitpick: isn't this secret read-only. And if yes, should it be ro instead of rw?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The key should be rw I want my cronjob to be able to write to the bucket. It's a readable secret for ESO i.e. ESO can read this secret but not modify it which is why its eso_readable_secret.

@naved001
naved001 merged commit 63c36af into CCI-MOC:main Oct 27, 2026
2 checks passed
@naved001
naved001 deleted the oac-prod-infra/b2-secret branch October 27, 2026 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants