Store sensitive variable values in Azure Key Vault
So sensitive project variables will be referenced from Azure Key Vault instead of being stored in octopus.
3357461 - 'Azure Resource Manager Key Vault support' was only about ARM template Key Vault support.
17973586 - 'Integrate Octopus deploy with secrets managment system Vault' is similar to this issue only for https://www.vaultproject.io
Pedro Luz commented
This is high priority given the community scripts for KeyVault are very faulty :(
The ability to keep secrets in a secure cloud location, integrated in Octopus, and be able to write them during deployment (say your terraform step created a database and you need to save the connection string) as well as read them/apply them to apps would be great.
Richard Nagle commented
Also please support AWS Secrets Manager
Greg Lloyd commented
This would greatly beneficial for our deployments as it provides a secure way access and version related secrets and configurations.