Skip to content

feat(helm): Add azure secret vault integration#3

Open
susilnem wants to merge 4 commits intodevelopfrom
feature/setup-secret-vault
Open

feat(helm): Add azure secret vault integration#3
susilnem wants to merge 4 commits intodevelopfrom
feature/setup-secret-vault

Conversation

@susilnem
Copy link
Member

@susilnem susilnem commented Mar 12, 2026

Addresses

  • Support azure vault integration

Changes

  • Update changes on env and secrets
  • update on deployments

@susilnem susilnem force-pushed the feature/setup-secret-vault branch from aa2856e to 5140a65 Compare March 13, 2026 04:04
Copy link
Member

@thenav56 thenav56 left a comment

Choose a reason for hiding this comment

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

Looking good

Copy link
Member

Choose a reason for hiding this comment

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

Let's break this down into multiple files.

values/
	- go-deploy.yaml <--- this will include config for when used with go-deploy
	- staging.yaml <--- this will include if any staging scoped application configuration

eg:
https://github.com/IFRCGo/montandon-etl/blob/develop/helm/values/go-deploy.yaml
https://github.com/IFRCGo/montandon-etl/blob/develop/helm/values/staging.yaml

Use XXX: go-deploy to specify this needs to be set in go-deploy. It will help to map variables easily in there

helm/values.yaml Outdated
Comment on lines +103 to +104
secretsKeyMap:
TRANSLATION_API_KEY: "TRANSLATION-API-KEY"
Copy link
Member

Choose a reason for hiding this comment

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

This should be in the values/go-deploy.yaml (is it depends on how the variables are set in the vault)

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.

2 participants