Bump Bicep.Types to latest to clear deprecation warnings and ensure backwards compatibility #11687
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
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.
Resolves #9572
This PR updates updates The
Az,K8s, andMicrosoftGraphtype factories to recognize and process the new constraint-bearing primitive type definitions introduced inAzure.Bicep.Types v0.4.1. The Az type generation workflow has been updated to use these new definitions when resource properties are constrained in the service model, so the next release of Bicep will include warnings when, for example, a string is too short or too long to be accepted as a resource name.Microsoft Reviewers: Open in CodeFlow