[feature request] azure yaml validator
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
Our team has developed the workflow that validates the operations of azd up and down are successful, in the context of curated collections. This pipeline workflows do not validate the shape or correctness of the azure.yaml configuration, which would be desirable before the CLI ran any template based operation, due to the tight coupling between the service configuration and the CLI API surface.
The idea would be that on, for example, `azd up`, the azure.yaml file was parsed and the shape analyzed, marking a correspondence between the Bicep definitions and the services configured.
If the check is successful, the `azure.yaml` file is preliminarily validated with a clear message to the user that services are configured, although that's not a guarantee of successful deployment.
If the provisioning and deployment relies on hooks, the azure cli or any other scripting mechanisms, a warning message should be printed to alert the user.
Contributor guide
Assessment
This issue has not been assessed yet.