Closed Dylan-Prins closed 2 years ago
@Dylan-Prins Thank for logging the issue. Yes, GitHub Action will scan the repository by default. This differs slightly from the cmdlet, but is the most common scenario which is why it is the default.
Add the inputType: 'inputPath'
parameter to the action to achieve the same result.
For example:
test:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
# Analyze Azure resources using PSRule for Azure
- name: Analyze Azure template files
uses: microsoft/ps-rule@v2.2.0
with:
modules: 'PSRule.Rules.GitHub'
inputType: 'inputPath'
Indeed this works. I was expecting that with 'repository' that the module would find the json file and then have the same results... Thanks anyway
Description of the issue
Thanks for the solution earlier, that works great. I have the same thing with the GitHub actions. It is like its scanning the repository files instead of the GitHub export
To Reproduce
Steps to reproduce the issue:
Expected behaviour
A clear and concise description of what you expected to happen.
Error output
Capture any error messages and or verbose messages with
-Verbose
.Module in use and version:
Captured output from
$PSVersionTable
:Additional context
Add any other context about the problem here.