-
Notifications
You must be signed in to change notification settings - Fork 728
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
Suggestion - provide standard constraint sets or types for parameters #2481
Comments
I'm pretty sure we have another issue for this, but I can't find it. We definitely want to do this and combine it with what we have planned for #622 Something like: param skuName Web.Sites.Sku Name is a little more complex as each resource type may have different naming requirements. So it is not possible to have a generic AzureName type, we could have something like @rynowak also has an interesting proposal in #1602 that would not require the parameter to be explicitly declared and we would have all they type info we need because we have the context for where it will be used. |
I like your syntax better than mine :-) I wasn't particularly hung up on |
I just decompiled a standard "website" ARM template and was rewarded with this code....
I understand that the decompiler is just mechanically ripping this out of the ARM json but wouldn't it be a lot terser and human-friendly to be able to generate something like
where AzureName and AzureWebSku are simply predefined in the tooling (and sourced from the actual Azure constraint schema).
The text was updated successfully, but these errors were encountered: