The conversion script is unable to deal with the Microsof.Authorization namespace pipelines as they are not referenceing the main deploy.bicep file, but sub_deploy.bicep files and the like.
In the current version of the logic, these references are simply not updated. In a soon to be merged version, they are at least updated to .json. However, this won't solve the problem just yet, as templates like sub_deploy.bicep don't exist in the module's root, but its .bicep folder. As this folder is not just not converted to JSON, but actually deleted, we have to find a different solution.
The easiest might be to reference deploy.json for this namespace post conversion instead. However, as this may still cause problems (e.g. due to a lack of permissions), this must be documented.
Still better as no solution, I guess.
The conversion script is unable to deal with the Microsof.Authorization namespace pipelines as they are not referenceing the main
deploy.bicepfile, butsub_deploy.bicepfiles and the like.In the current version of the logic, these references are simply not updated. In a soon to be merged version, they are at least updated to
.json. However, this won't solve the problem just yet, as templates likesub_deploy.bicepdon't exist in the module's root, but its.bicepfolder. As this folder is not just not converted to JSON, but actually deleted, we have to find a different solution.The easiest might be to reference
deploy.jsonfor this namespace post conversion instead. However, as this may still cause problems (e.g. due to a lack of permissions), this must be documented.Still better as no solution, I guess.