microsoft / microsoft/security-devops-azdevops
Error running pipeline
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Hi there. I have a simple bicep pipeline running installing a scale set through modules that are sat in a private container registry. I have this working with PSRule and is working nicely.
I am getting a few errors while trying to get this working, and there is limited documentation. Any help would be great.
| Error running templateanalyzer job: 1 of 1Lint and scan code • Defender for DevOps • Microsoft Security DevOps | |
| GuardianErrorExitCodeException: templateanalyzer completed with an Error exit code: 21. Error: An error was encountered trying to analyze a templateLint and scan code • Defender for DevOps • Microsoft Security DevOps | |
| Error running tool 2 of 3: templateanalyzerLint and scan code • Defender for DevOps • Microsoft Security DevOps | |
| Error running templateanalyzer job: 1 of 1Lint and scan code • Defender for DevOps • Microsoft Security DevOps | |
| GuardianErrorExitCodeException: templateanalyzer completed with an Error exit code: 21. Error: An error was encountered trying to analyze a templateLint and scan code • Defender for DevOps • Microsoft Security DevOps | |
| MSDO CLI exited with an error exit code: 1Lint and scan code • Defender for DevOps • Microsoft Security DevOps
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Azure DevOps pipeline with the Bicep modules in the private container registry and inspect the templateanalyzer output around exit code 21. Compare the failing run with the working PSRule setup; done means the templateanalyzer and MSDO CLI complete without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100