Describe the bug
Similar to #2641, the new Bicep version 0.14.6 introduces a change that will require us too roll out updates across a range of modules. In this case, the ARM schema type secureString was intentionally changed to securestring which in turn requires our module readme's to change the casing to once the new version is rolled out to the Microsoft-hosted agents. By the time of this issue's creation, they still operate on 0.13.1.
This issue is linked to the closed issue in the Bicep Repository (cc: @ahmadabdalla).
Once the change becomes available on the agents we'll have to run the Set-ModuleReadMe script on all modules and migrate them to the new convention.
To reproduce
Once 0.14.6 is available, the Set-ModuleReadMe script will want to change the casing of all occurences of secureString to securestring.
Relevant log output
Describe the bug
Similar to #2641, the new Bicep version
0.14.6introduces a change that will require us too roll out updates across a range of modules. In this case, the ARM schema typesecureStringwas intentionally changed tosecurestringwhich in turn requires our module readme's to change the casing to once the new version is rolled out to the Microsoft-hosted agents. By the time of this issue's creation, they still operate on0.13.1.This issue is linked to the closed issue in the Bicep Repository (cc: @ahmadabdalla).
Once the change becomes available on the agents we'll have to run the
Set-ModuleReadMescript on all modules and migrate them to the new convention.To reproduce
Once
0.14.6is available, theSet-ModuleReadMescript will want to change the casing of all occurences ofsecureStringtosecurestring.Relevant log output