azure / psrule.rules.azure-quickstart Goto Github PK

I've just cloned this repo into my Azure DevOps org, added a pipeline based on .pipelines/azure-analyze.yaml, made one small change (see screenshot below) to generate a fail, and ran the pipeline.

The pipeline runs, but fails—is it meant to fail given I've literally just cloned the repo and made a small modification? In short, I'm unsure of what the expected output should be. I'm not sure if everything is working as expected or there is indeed something broken within this repo or the pipeline has changed its behaviour.

I've included the screenshots of the pipeline job so I'd appreciate it if you/I/we can work through it together.

So the below screenshot shows an error against AZR-000355 which I'm expecting given the modification I made. That's fine. I'm guessing the next line, "One or more assertions failed" is also fine since that is true.

This next screenshot shows the warnings.

• I'm not sure why that first warning ("refs/heads/main has not been processed") is there?
• Apart from the suppressed rules, what do the other warnings mean about "not been processed because no matching rules were found" and how do I correct this
  

The next screenshot shows the Extensions tab.
This looks fine to me.

Finally, there are no artifacts produced (under the Scans tab) as the pipeline never got to that task.

From what I've seen in the YT videos and my expectations given the minimal modifications, the job should complete with a status of Warning as opposed to Failed so that one can view the prettyfied output under Scans?

Edit: ok so I just re-read some of the documentation and have configured the pipeline to continue on error. Now I can see the Scans output which is great. But if this is set to true just so I can get some pretty outputs, then wouldn't it be more suited to permanently leave this to true?

Thank you and I appreciate your time!

Most customers with interest in PSRule for Azure are moving to Bicep from ARM templates. We should:

• Archive the current repo structure into a branch archive/with-arm-templates.
• Remove directories and anything specific to ARM templates.
• Flatten the repository to root deployments/ and modules/ paths that focus on Bicep.
• Add a link to readme to flag old ARM template structure is available in the archive branch.
• Update any documentation to focus and make Bicep configuration clear and easily usable by customers.