Deployment Stacks: Expose configurable settings for actionOnUnmanage and denySettings#4331
Conversation
2128026 to
7d3550d
Compare
vhvb1989
left a comment
There was a problem hiding this comment.
Let's gather more information around using azure.yaml before merging this.
I think a little more conversation would be beneficial for similar future changes.
Based on team's conversation, we don't care enough about what settings we add to azure.yaml v/s config.json; specially for Alpha features.
c31e94a to
0385a2b
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
weikanglim
left a comment
There was a problem hiding this comment.
LGTM. We'll experiment with the config changes as they're presented and iterate as we get feedback.
Add new optional
deploymentStackssection for the infra provider to pass settings for deployment stacks.Since
azdsupports pluggable infrastructure providers thedeploymentStacksproperty within theinfrasection of theazure.yamlis lazily validated during provision command.Example Usage:
The following is an example showing custom configuration options for deployment stacks.
Default Configuration
The following is the internal defaults for deployment stack options when not overridden within the
azure.yamlfile.bypassStackOutOfSyncError : false
actionOnUnmanage:
deletefor all typesdenySettings:
nil(No deny settings by default)Overrides
Users can override
bypassStackOutOfSyncErrorby setting OS env varDEPLOYMENT_STACKS_BYPASS_STACK_OUT_OF_SYNC_ERRORto a truthy value.Resources
See official deployment stacks docs for full list of available configuration options.
More Docs