Deployment fails if there is parameter in *.json that bicep file does not use it

[uky2019]

Hi all,

I am deploying environment in Azure and would like to have a central parameter *.json file for all my bicep files (I have several).

I am reading this same parameter file with any of the bicep deployment files, but deployment fails if there is a parameter in that json file that is not then used in bicep deployment file. This is expected as not all deployment ofcourse use the same parameters...

I want to keep just one central parameter file, how can I overcome this issue?

[uky2019]

I found a sort of workaround for this, If I use modules I can specify "unique" parameters there for each specific bicep file I am referencing it, but then using parameter file (*.json) does not work? If anybody have some insight I would be grateful.

thanks

[kevball2]

If a parameter is listed there needs to be a matching parameter in your bicep file. You don't have to use it, but it does have to be there.

You can organize your parameters as part of an object and then use the parameters that you need in that deployment. A good sample can be found here

[uky2019]

It never crossed my mind to just put it there and not use it, since intelisense underlines it as errror as param is never used. Regarding organizing parameters objects, thats is a great Idea I am in middle of redoing my whole parameter file this is awesome and much more clearer, your answer can be marked as solution, big thanks !

[kevball2]

While that will work, I would state my preference would be to use environment specific parameter files for your deployments. I don't know if there is a size limit for the parameter file like with the arm template itself, if so, having a single large parameter file will cause issues later.

If you want to minimize the number of parameter files you have to manage, you should focus on consolidating your deployments to an application or subscription level.

All these options really depend on how many resources you need to deploy and how often.

@brwilkinson has a great project for deploying at the subscription level - ADF
There is also the Bicep Azure Landing Zone

[brwilkinson]

if you do go the unused param, you can also tag it to avoid any linting errors.

#disable-next-line no-unused-params
param Stage

[uky2019]

For now parameter file is small it will grow with time but I do not think it will become a problem, if it does I will keep this in mind.

[uky2019]

I do not know how to mark @kevball2 reply as answer mods please do it.

[brwilkinson]

Well @uky2019 since @kevball2 replied under your original answer, we cannot set him specifically as answering, however we can send him huge thank you and appreciation 🙂👍🏼🙏🏼✅⭐

I will mark as answered, ... we appreciate your discussion points, so also thanks to you.