add support for bicep decorator value constraints#3828
Open
polatengin wants to merge 11 commits into
Open
Conversation
… and output value constraints
…ut value constraints
polatengin
added
enhancement
BernieWhite
approved these changes
Jun 11, 2026
BernieWhite
left a comment
BernieWhite
left a comment
Collaborator
There was a problem hiding this comment.
Great work @polatengin. All good to merge.
This file contains hidden or 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
2 participants
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.
Summary
Fixes #3649
Adds support for validating ARM template value constraints emitted by Bicep decorators on parameters and outputs.
This adds the new
Azure.Template.ValueConstraintrule to check resolved values against:allowedValuesminLengthmaxLengthminValuemaxValuevalidateFor
@validate, the compiled ARM lambda expression is evaluated and any custom validation message is used as the rule reason.PR Checklist