You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened? Provide a clear and concise description of the bug, including deployment details.
When using the bicep accelerator, a env file is generated where UPSTREAM_RELEASE_VERSION sets the version of the golder under uppstream releases.
Currently the version you get is 0.16.6, while the generated value in the env file is 0.16.5. This will make the pipeline fail, as it use the env file to generate correct paths.
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
Env file having correct version number.
Relevant log output
No response
Check previous GitHub issues
I have searched the issues for this item and found no duplicate
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
@jaredfholgate has worked his magic and we have fixed this in a new release of the ALZ PowerShell module v0.2.22 please upgrade to that and your issue should be solved
What happened? Provide a clear and concise description of the bug, including deployment details.
When using the bicep accelerator, a env file is generated where UPSTREAM_RELEASE_VERSION sets the version of the golder under uppstream releases.
Currently the version you get is 0.16.6, while the generated value in the env file is 0.16.5. This will make the pipeline fail, as it use the env file to generate correct paths.
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
What was the expected outcome?
Env file having correct version number.
Relevant log output
No response
Check previous GitHub issues
Code of Conduct
The text was updated successfully, but these errors were encountered: