-
Notifications
You must be signed in to change notification settings - Fork 13
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Referencing PSRule main branch #212
Comments
@Gordonby I might not be understanding the issue correctly so please correct me. PSRule v2.7.0 is the latest version, and the GitHub Action Using The If you would like to install a different PSRule version with the For example, the following would use the latest action but install PSRule v1.11.1. - name: Run PSRule analysis
uses: microsoft/ps-rule@main
with:
version: '1.11.1' See usage So if you want to install latest stable version of everything just use: - name: PSRule for Azure - Well Architected
uses: microsoft/ps-rule@main
continue-on-error: true #Setting this whilst PSRule gets bedded in, in this project
with:
modules: 'PSRule.Rules.Azure'
inputPath: "${{ env.ParamFilePath }}" I hope that helps. |
Perhaps I'm conflating the 2 repos. #whoops My aim is to test what was committed in this PR. |
@Gordonby Sure no problem. You should get the latest version with the So try: - name: PSRule for Azure - Well Architected
#uses: microsoft/ps-rule@v2.7.0
uses: microsoft/ps-rule@main
continue-on-error: true #Setting this whilst PSRule gets bedded in, in this project
with:
modules: 'PSRule.Rules.Azure'
inputPath: "${{ env.ParamFilePath }}"
prerelease: true This should install the latest prerelease version PSRule for Azure which would be |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Is your feature request related to a problem? Please describe.
The current PSRule release is 3 weeks old.
I wish to test a recent change in the main branch.
I tried using both of these syntaxes, however the first continued to reference 2.7.0 and the second failed. Apologies if this is documented somewhere that i didn't spot.
Describe the solution you'd like
An easy way to use the version in main
Describe alternatives you've considered
None
Additional context
https://github.com/Azure/AKS-Construction/blob/gb-wellarchfixup/.github/workflows/ByoVnetCI.yml
The text was updated successfully, but these errors were encountered: