have a better way of handling parameters in arm templates
When setting up a new ARM template for use in octopus we set the default value of all parameters to #{something} so that the 'parameter' page in octopus is auto populated.This works great for most values but if we have a secure string octopus will update the 'default value' in the arm which will show up in the deploy history in Azure. We would like to see some way to handle this so we can ignore updating the default value or auto-populate the parameters page without needing the default value or some other way to handle this a bit cleaner.
1
vote
