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.
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events