[Breaking Change] Deprecate provider
in Bicep configuration files
#14468
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.
Decided to implement this change as a breaking change rather than a soft deprecation because:
providers
andextensions
are quite expensive without altering the configuration file binding logic (binding after merging the custom configuration into the built-in configuration).providerRegistry
experimental feature is used exclusively by the Bicep team internally, so the change poses minimal risk.Closes #14377.
Microsoft Reviewers: Open in CodeFlow