-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check that Portal UI form outputs map to template parameter inputs on pull requests #620
Conversation
adding a check that the form is indeed a form and the deployment template is indeed a template this could be done in the future with some schema validation, but, this'll do for now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is 🚀 🦖 🎉 . The README was easy to follow and I was able to reproduce everything documented there, including testing mismatched form and parameters. I had one issue with building the dev container, but I added a suggestion to fix it.
If you think this is a general purpose tool, in the future it could move to https://github.com/glennmusa and we could reference it there.
I like your idea to make use of this as a general purpose tool from a different repository:
I'll update this branch so that it makes use of the tool in a pipeline, but host that tool elsewhere. Thanks for the idea. |
Thanks for the thorough review @brooke-hamilton! I've taken your advice and now host this tool here: https://github.com/glennmusa/validate-declarative-form It's extremely lightweight today to |
* Check that Portal UI form outputs map to template parameter inputs on pull requests (#620) * Move the workflow scripts to where they're used (#632) * Update descriptions in alt text on main README.md (#633) * Add spike issue template and remove feature request issue template (#635) * Fix for Terraform issue in which the tier 2 subscription parameter is ignored (#638) * Process for handling a broken build (#641) * Clean-up nightly deployments using Azure CLI (#642) * Add instructions for ASC/Defender cleanup (#643) * Pin Bicep to v0.4.1272 (#650) * SBOM generation in PR (#648) * Update policy assignment resource provider version (#652) * Generate SBOMs without .git contents (#654) * Generate SBOM files during PR events (#656) * check to see if the SBOM needs to be regenerated before running the pipeline again * Update Software Bill of Materials (SBOM) Co-authored-by: Microsoft.VisualStudio.Services.TFS <> Co-authored-by: Glenn Musa <[email protected]> Co-authored-by: Brooke Hamilton <[email protected]> Co-authored-by: Vidya Bala <[email protected]> Co-authored-by: JeromeJansen <[email protected]>
Description
So that:
Here's what it looks like when this check fails:
https://ag-ascii.visualstudio.com/Mission%20Landing%20Zone%20-%20Pipeline/_build/results?buildId=6746&view=results
Here's what it looks like when this check passes:
https://ag-ascii.visualstudio.com/Mission%20Landing%20Zone%20-%20Pipeline/_build/results?buildId=6756&view=results
These proposed changes:
/main
mlz.portal.json
declarative form andmlz.json
deployment template are validated and if any errors occur, the pipeline failsIssue reference
The issue this PR will close: #598
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: