Skip to content
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

Support Bicep complete mode in azd provision #4241

Open
rajeshkamal5050 opened this issue Aug 23, 2024 Discussed in #2519 · 1 comment
Open

Support Bicep complete mode in azd provision #4241

rajeshkamal5050 opened this issue Aug 23, 2024 Discussed in #2519 · 1 comment

Comments

@rajeshkamal5050
Copy link
Contributor

Discussed in #2519

Originally posted by bioerrorlog July 12, 2023
Bicep's default deployment mode is Incremental mode, but I want to manage the resources in Complete mode.

In bicep, the --mode option can be used to specify the deoloyment mode, but how can I specify it in azd?

@rajeshkamal5050 rajeshkamal5050 added this to the Backlog milestone Aug 23, 2024
@rajeshkamal5050 rajeshkamal5050 changed the title Support Bicep complete mode in azd Support Bicep complete mode in azd provision Aug 23, 2024
@weikanglim
Copy link
Contributor

weikanglim commented Sep 16, 2024

With deployment stacks, resources that are not tracked in Bicep is automatically deleted. I wonder if this is in some ways, better for our users here and so we should avoid adding Bicep Complete mode as a feature.

The only slight difference between deployment stacks and Complete mode in Bicep is that: In complete mode, other resources not tracked in the resource group is automatically deleted. Compared to deployment stacks, where the source of truth is the Bicep files themselves.

Added a discussion answer here referencing deployment stacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants