Azure / Azure/bicep

provide sending params files to modules

Open
#11,803 0 comments 1 reaction 0 assignees View on GitHub
enhancement Needs: Upvote
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

**Is your feature request related to a problem? Please describe.**
Customer has currently 1 JSON ARM template that they are deploying multiple times in a AzDO deployment pipeline with each time a different parameters file. This gives them the problem that deployment takes a long time, since each time a new calc needs to be made of the diff in the resource group. They end up with 30 times a deploy time between 3-5 minutes, so ending up at a total deploy time of around 1 hour.
Advise I gave for now: Create a master template, where you reference your template multiple times as a linked template and then send a different parameter file for each deployment of the linked template. But, I was also thinking: You can also use Bicep for the master template and then reference the existing JSON ARM template through a module. BUT, and this is the restriction in Bicep: it doesn't allow you to just reference a parameter file in a module, you can only reference the params one by one. Customer would like to send the params file and be done with it.

**Describe the solution you'd like**
Allow for params file on module call and not only param by param.

See tryout branches at https://github.com/vermegi/vscode-remote-try-bicep/tree/main tryout 2 and 3 are functional alternatives, although still cumbersome.

Contributor guide

Open the contributing guide

Research direction

Review the issue's tryout 2 and 3 branches and the existing module-call and parameter-file behavior described there. Determine the supported syntax and validation path for passing a parameter file to a module; done means a module can consume the file directly and the relevant deployment scenarios work without one-by-one parameter mapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.