You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I would like to manage my secrets/variables in one place. It feels error prone and "un-GitOps" to be hand editing long lists of variables in the Bitbucket interface for each repository.
I am working with Azure and so there are many common variables required for each build (service account credentials, Kubernetes cluster details, Container Registry details, Maven repository details etc.).
Would it be possible to source variables from something like a Key Management Solution? (in my case Azure Key Vault but I understand other similar solutions exist, GCP KMS, AWS KMS etc).
Currently Pipeline has no native way to populate environment variables from external key management solutions. You can open a feature request for those types of integrations here: https://bitbucket.org/site/master/issues/new
For now, you would have to start your build script by retrieving the variables from the external key management solution and then source them, before running the rest of your build.