-
Notifications
You must be signed in to change notification settings - Fork 40
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
[FEATURE REQ] Support Parameters "allowedValues" property #314
Comments
I ran into an issue with @Allowed parameters and am not sure if it's a bug with template-analyzer, a bug with our Bicep, or if it's this bug. Specifically: We have functions.bicep with these params:
That
The bicep checker is okay with this, but template-analyzer errors (fatally) and says:
See full run: https://github.com/pamelafox/simple-flask-server-example/actions/runs/4492526898/jobs/7902534396?pr=3 Are we required to specify a default in functions.bicep for this scenario? Or is this a template-analyzer parsing issue? (And if so, is it the one described above?) Thanks! |
Any update on this? We are getting this issue as well when we have a parameter that needs to be a specific allowed value and if a parameter file is not provided the text generated does not match. |
Please describe the feature or suggestion.
Template parameters can have an array defined specifying what values are allowed for the parameter.
https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/parameters#allowed-values
Currently, if a parameter has allowed values specified, template parsing (without using a parameters file) throws an exception because a mock value is used that (very likely) will not be an allowed value.
BPA should be able to pick a value from this list and use that for the parameter value instead of making up a value on its own.
Additional context
This could also be considered a bug, but I'm filing the issue as a feature request.
The text was updated successfully, but these errors were encountered: