-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make appSettings
a secure object by default
#2575
Conversation
Repoman Generation ResultsRepoman pushed changes to remotes for the following projects: Project: todo-csharp-cosmos-sqlRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-csharp-cosmos-sql -b pr/2575 View Changes | Compare Changes Project: todo-csharp-sql-swa-funcRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-csharp-sql-swa-func -b pr/2575 View Changes | Compare Changes Project: todo-csharp-sqlRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-csharp-sql -b pr/2575 View Changes | Compare Changes Project: todo-java-mongo-acaRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-java-mongo-aca -b pr/2575 View Changes | Compare Changes Project: todo-java-mongoRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-java-mongo -b pr/2575 View Changes | Compare Changes Project: todo-nodejs-mongo-acaRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/2575 View Changes | Compare Changes Project: todo-nodejs-mongo-aksRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-nodejs-mongo-aks -b pr/2575 View Changes | Compare Changes Project: todo-nodejs-mongo-swa-funcRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/2575 View Changes | Compare Changes Project: todo-nodejs-mongoRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-nodejs-mongo -b pr/2575 View Changes | Compare Changes Project: todo-python-mongo-acaRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-python-mongo-aca -b pr/2575 View Changes | Compare Changes Project: todo-python-mongo-swa-funcRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-python-mongo-swa-func -b pr/2575 View Changes | Compare Changes Project: todo-python-mongoRemote: azure-samples-stagingBranch: pr/2575You can initialize this project with: azd init -t Azure-Samples/todo-python-mongo -b pr/2575 View Changes | Compare Changes |
Is there a user reported issue that this resolves? If so, please add a link/reference. |
@wbreza Linked. |
@weikanglim After reviewing the linked issue its unclear on whether this would workaround the issue since we're still using a param We may want to look into using keyvault reference from the app service app setting. |
This allows users to set secret values as app settings for
appservice
,function
host services. App service handle secrets in app settings by defaults, so there isn't any additional configuration there.Fixes https://github.com/Azure/azure-dev-pr/issues/1563