Use Azure Key Vault for Container App Secrets #374
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DrizzlyOwl
force-pushed
the
use-key-vault-for-secret
branch
4 times, most recently
from
232ff47 to
492ce72
Compare
Stretch96
approved these changes
May 30, 2024
DrizzlyOwl
force-pushed
the
use-key-vault-for-secret
branch
from
492ce72 to
73f8a9b
Compare
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change migrates Container App Secret Environment Variables into Key Vault Secrets.
In order for this to deploy successfully, the Container App Managed Identity must be granted the Key Vault Secret User role so that it can read the values from Key Vault when the Container boots.
If you already have a Key Vault deployed, you can leverage it by setting the
existing_key_vaultvalue.