Target object has not been processed because no matching rules were found, but starts analyzing right after? #1422
-
|
Then
What is causing this? Build always starts like this for all modules, but still analyzes them right after. For information, main.test.bicep is just referring to main.bicep, but with required parameters.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
@bengeset96 PSRule for Azure doesn't include any rules that test the Bicep files directly. Instead we export the Azure resources, which is the reason for the warning. We could do better explaining this and providing a different default behaviour. An examples of a rule that does target the file would be:
Your code is fine. If you want to disable the warning configure the configure the For example, you can do this in execution:
notProcessedWarning: falseOther options on how to configure this are available in the docs. I hope that helps. |
Beta Was this translation helpful? Give feedback.
-
|
It makes sense! Thank you for the clarification. I added this yesterday and it solved all my cosmetic "issues". |
Beta Was this translation helpful? Give feedback.
@bengeset96 PSRule for Azure doesn't include any rules that test the Bicep files directly. Instead we export the Azure resources, which is the reason for the warning. We could do better explaining this and providing a different default behaviour.
An examples of a rule that does target the file would be:
main.bicepor looking for a readme in the same path.Your code is fine. If you want to disable the warning configure the configure the
Execution.NotProcessedWarningoption.For example, you can do this in
ps-rule.yamlby:Other options on how to configure th…