Azure / bicep-registry-modules

Bicep registry modules
MIT License
520 stars 366 forks source link

[Failed pipeline] avm.platform.check.psrule #1420

Open github-actions[bot] opened 8 months ago

github-actions[bot] commented 8 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8425262943

github-actions[bot] commented 8 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8490211311

github-actions[bot] commented 8 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8497975277

eriqua commented 8 months ago

The failure of this pipeline is currently expected. This platform pipeline is running PSRule on the whole library. This includes all the 5 WAF pillars, not only the reliability pillar. It will stay in this state until all PSRule checks, for all pillars and for all modules, are successful.

We can proceed in 2 ways:

  1. Keep this issue open, knowing it will stay open for a long time, likely months
  2. Exclude this workflow from the failed pipeline automation

@matebarabas if we go with option 1, can we triage this accordingly in terms of automatic replies, labels etc?

github-actions[bot] commented 8 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8534319544

eriqua commented 8 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8534319544

For example, if we go with option 1 we should avoid adding a failed run comment every day. We could introduce a label "known issue" and pause the automation(s) on it

avm-team-linter[bot] commented 7 months ago

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8772447020

krbar commented 2 months ago

@Azure/avm-core-team-technical-bicep The affected pipeline seems not to exist anymore, can we close this issue?