`inputPath` set to `some.bicepparam` file works, but throws warning `has not been processed because no matching rules were found`

[o-l-a-v]

`inputPath` set to `some.bicepparam` file works, but throws warning `has not been processed because no matching rules were found`

[BernieWhite]

@o-l-a-v In part it does, but not by a rule.

If Bicep generates a Error either via a linter rule that is set to error or a general compile issue PSRule will propagate the error up and generate an error, which will result in breaking the build. But there is no rule that drives this, so a warning would still be generated.

[BernieWhite]

Hi @o-l-a-v this is intended. The behaviour will change in PSRule v3, because it is a common cause for confusion.

---

Expanding my explanation, by default, PSRule will warn objects that are processed and no rules have run. Each file is treated as an independent object in addition to the Azure resources contained within.

Because you have no rules that check this object (PSRule for Azure doesn't ship with any) the warning is generated.

You can toggle of the warning by setting the Execution.UnprocessedObject option to Ignore.

See: https://microsoft.github.io/PSRule/v2/concepts/PSRule/en-US/about_PSRule_Options/#executionunprocessedobject

---

If there is no further issue, let's close this issue.

[o-l-a-v]

Thanks for the explaination @BernieWhite.

I wrongfully assumed PSRule analyzed the results of Bicep build.