Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

env file is generating wrong UPSTREAM_RELEASE_VERSION #684

Closed
2 tasks done
JimmyKarlsson112 opened this issue Nov 16, 2023 · 5 comments
Closed
2 tasks done

env file is generating wrong UPSTREAM_RELEASE_VERSION #684

JimmyKarlsson112 opened this issue Nov 16, 2023 · 5 comments
Assignees
Labels
Needs: Attention 👋 Needs attention from the maintainers

Comments

@JimmyKarlsson112
Copy link

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
@jtracey93
Copy link
Collaborator

Hey @JimmyKarlsson112,

Thanks for the bug. Can you confirm what version of the ALZ PowerShell module you are using?

Is it the latest 0.2.21?

Let us know

@JimmyKarlsson112
Copy link
Author

Np,
Yes, the latest, 0.2.21

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs: Attention 👋 Needs attention from the maintainers and removed Needs: Author Feedback labels Nov 16, 2023
@jtracey93
Copy link
Collaborator

Thanks for confirming @jaredfholgate is looking into this

@jtracey93
Copy link
Collaborator

Hey @JimmyKarlsson112,

@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

https://www.powershellgallery.com/packages/ALZ/0.2.22

@JimmyKarlsson112
Copy link
Author

Thanks team awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Attention 👋 Needs attention from the maintainers
Projects
None yet
Development

No branches or pull requests

3 participants