No rules are being processed

[Crowiiie]

Hi,

I have already checked out the #1332, but unfortunately keep running into a wall with getting this to work.

I have set up a .ps-rule folder within my repository, which contains the files bicep.Rule.ps1:

I have also set up a templates folder, which contains a main.bicep file:

I have set up the ps-rule.yaml file in the root:

I then have a pipeline which installs the dependencies and runs the Assert-PSRule:

Unfortunately it seems like it is unable to find my custom rule, given that it processes 0 rules:

I assume I am missing something somewhere, but I have unfortunately gotten to a point where I don't know where to look anymore. I have attempted using the example in the documentation (https://microsoft.github.io/PSRule/v2/scenarios/validation-pipeline/validation-pipeline/#complete-example), but it only works when the folder to analyze is the .ps-rule. This seems like an awesome extension and I would really like to get it working.

Any idea where I am going wrong? :)

[BernieWhite]

@Crowiiie Thanks for the question. Three things to try that should resolve this.

Use PSRule for Azure

Azures resources from a Bicep file are a little tricky because they need to be expanded (to resolve parameters, variables, functions, and modules). We've already done a lot of the work through PSRule for Azure. Have a look here Installation and Creating your pipeline. The AZURE_BICEP_FILE_EXPANSION configuration option in your ps-rule.yaml is for PSRule for Azure, and won't work if it is not installed.

If you do not want to use the Azure Pipeline task installable from the Visual Studio Marketplace suggested by these docs, which is the simplest path, then:

• Install PSRule for Azure by using Install-Module PSRule.Rules.Azure, this would also install the PSRule module automatically, so a separate command is not required.
• Update your Assert-PSRule command-line to include -Module PSRule.Rules.Azure -Format File to use the PSRule for Azure module.
• Set -InputPath to where you bicep files are or the whole repo instead of .ps-rule/. From whichever path you choose, PSRule will automatically scan all subfolders. For example -InputPath . or -InputPath '**/*.bicep'.

Update the type for the custom rule

Instead of using Microsoft.Storage/storageAccounts@2021-09-01 in your rule, just use Microsoft.Storage/storageAccounts. The @2021-09-01 refers to the API version which is not strictly part of the resource type.

Configure type bindings for local rules

Set the binding.targetType option in ps-rule.yaml as described here Binding type.

For example:

# Configure binding options
binding:
  targetType:
  - 'resourceType'
  - 'type'

---

I hope that helps.

[Crowiiie]

Thank you for taking the time to write out such a comprehensive answer! I have implemented the changes suggested above, and now both the Azure Pipeline task and the Powershell script options are working properly. 👍