Azure Resource Manager
-
Increase Keyvault Reference Limit in Parameters from 29 to 60+
As of right now, the communicated limit for keyvault references in a parameters file is "30", but is actually in practice 29 (appears to be a bug?).
This limitation is quite low for mature systems. Take, for example, the following potential data points:
- Multiple SQL ids/passwords, storage account keys, AI instrumentation, Redis cache credentials, etc. for connection strings
- App to app communication creds/API keys
- Programmatically created dynamically named/numbered resources
- References to signing keys for different purposesMany of the clients I work with are struggling with this issue, which seems easily fixable by increasing the limit…
16 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog. Since this request came out of an escalation, I’ve engaged the feature owner to take a look and suggest next best step to validate and resolve the reported bug.
-
Set schedule to delete deployments history
Currently, The deployment history limits are 800 per resource group so if we will use many resources for long term, we might be upper limit.
I hope we can use a feature that setting schedule to delete the history.14 votes -
Run Ansible/Chef/Salt on deployment via ARM
When you deploy a Linux or Windows virtual machine deployment, via ARM. Allow an Ansible playbook to be run.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
[Request] Suggession on Deployment Modes in Azure
Hi Microsoft Team,
I really appreciate the Microsoft efforts for rapidly catching up market for Azure.
I have little suggestion over here for Azure Dev ops CI/CD using ARM Templates.There are two options given for deployment mode. i.e "Incremental" and "Complete".
"Complete" Mode of deployment deletes the existing services under that Resource Group. Even though it will be useful to discard unwanted services, still it is very dangerous. 'An Err is Human.' By mistake if this option is selected in pipline then all the services will be deleted and its difficult to restore it. This leads to raising support tickets…1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
Allow actual output of type "securestring"
When defining ARM outputs, "securestring" is a valid type, but nothing is actually outputted. This raises the question as to why it's a valid type, if it serves no purpose.
The "securestring" should be returned for further processing. (Alternately, there should be a schema error for specifying a type that can't work.)
Additional discussion at https://github.com/MicrosoftDocs/azure-docs/issues/32931.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
CopyIndex - add staged length for count
Add CopyIndex function to allow a numerical length to count. Enterprise may have their naming standards end with "01", "02", "03", etc. CopyIndex currently will only count logically from 0. "1" "2" "3", etc.
Suggested framework:
CopyIndex(loopName, offset, stagedlength)Suggest framework example:
CopyIndex('VM',1,000)Results would be:
VM001
VM002
VM003
VM0041 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
Allow usage of function arrays in the dependsOn section
The dependsOn section needs an array of strings, and each string added can call some functions like resourceId, parameters, and variables. But it does not accept a parameter or variable that contains an array of strings. It also doesn't allow the use of copy.
Allowing this would make it much easier (actually make it possible) to dynamically generate a list of dependencies based on parameters.
For instance, creating alerts links to action group resources. It is very likely that the action groups to use are given as a parameter (array of strings). Converting those strings to resourceIds (multiple) is easy…
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
- Don't see your idea?