Azure/ALZ-Bicep

custom-parameters, azuredevops\pipelines and pipeline scripts

Closed this issue · 2 comments

gerrynicol commented

Let us know the feedback or general question

Hi there,

Quick question on the above three folders in the directory tree. If I want to customise the names in the parameter files in custom-parameters is the best option to create new parameter files in the custom-parameters folder (as otherwise the vaules I set seem to get overwritten with every new release). I undertsand I would then have to update the devops pipeline scripts to reflect this. Also I would have to update the Deploy*.ps1 scripts in the pipeline-scripts folder. Or is there any easier way to do this?

Code of Conduct

  • I agree to follow this project's Code of Conduct
gerrynicol commented

I think I've got a solution to this. After updating the parameter files with my updated resource names, just take a copy of the parameter files and place in the custom-modules folder. After an update, just replace the 'new ones' with the saved ones.. Also have to update the .env file. Is this a sensible solution?

oZakari commented

Hi @gerrynicol,

You have uncovered a bug. 🙂 Your temporary solution makes sense, but we will work on fixing that. The parameter files should not be replaced during an upgrade. We need to add a toggle to the Deploy-Accelerator cmdlet to prevent it from affecting the custom-parameters directory if an upgrade switch is toggled.

A new version of the Accelerator is coming out soon. While we will continue to support the old Accelerator for some time, we recommend checking out the new version, which will be included in release v0.19.0.