Deprecation of notProcessedWarning

[Danielsn116]

Hi all!

I was working on moving towards the option execution.UnprocessedObject: Ignore in stead of the soon deprecated: execution.notProcessedWarning: false option. But on my pipeline it not seems to do what i would expect.

We are using:

• PSRule v2.9.0
• PSRule.Rules.Azure v1.40.0

For starting ps-rule we use the azure pipeline task: ps-rule-assert@2

Details (on ps-rule.yaml config file)

When using execution.notProcessedWarning: false i'm getting the warning about deprecation but that is expected
##[warning]The option 'Execution.NotProcessedWarning' is deprecated and will be removed with PSRule v3. See http://aka.ms/ps-rule/deprecations for more detail. no warnings on files that could not be processed.

When changing this to execution.UnprocessedObject: Ignore i'm getting warnings in my pipeline like:
##[warning]Target object 'ps-rule.yaml' has not been processed because no matching rules were found.

Also tried to use RuleSuppressed: Ignore and SuppressedRuleWarning: Ignore but no effect.

Thnx in advance for your help!
Daniel

[Elinora White (BernieWhite)]

Hi Danielsn116, thanks for the question.

How you are going about setting this option appears to be correct. i.e. you are replacing execution.notProcessedWarning = false with execution.unprocessedObject = Ignore.

The problem may be with the syntax. Are you setting this option via ps-rule.yaml?

If you are this should look something like:

execution:
  unprocessedObject: Ignore

Noting in YAML:

• The execution and unprocessedObject should match case, since YAML is case-sensitive.
• The execution key is not indented.
• The unprocessedObject is indented with 2 spaces. YAML can be a bit specific, although it can handle a different number of spaces as long as it is done consistently.

Setting this option is other ways is documented here: https://microsoft.github.io/PSRule/v2/concepts/PSRule/en-US/about_PSRule_Options/#executionunprocessedobject

Hopefully that helps, otherwise let me know.

[Danielsn116]

You are totally right! It was the syntax/case. This is because of my inexperience with YAML.

I just copy pasted from the documentation where it said UnprocessedObject.
Now i changed it to unprocessedObject and it's solved!

Thnx!