You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Know that proposed changes don't affect a working solution.
Description
When a Pull Request is raised, attempt to deploy the source in some known environment, but with unique resources that are destroyed upon success or failure.
Acceptance Criteria
- run linter (done already by GitHub Actions)
- run bicep build/validate (done already by GitHub Actions)
- run terraform validate (done already by GitHub Action)
- run bicep az deployment what-if (will be done in AzDevOps, go touch a subscription and a cloud see if a deployment is possible)
- run terraform plan (will be done in AzDevOps, go touch a subscription and a cloud see if a deployment is possible)
The text was updated successfully, but these errors were encountered:
Not all changes require a full deploy and teardown test. For example, documentation updates and issue templates changes. It would be nice if we could have the automation determine when full deploy is required based on the folder(s) containing the changed files.
brooke-hamilton
added
dev-automation
Related to automating builds, the development container, and improving the developer experience.
and removed
core
New feature or request
labels
Sep 1, 2021
Benefit/Result/Outcome
Know that proposed changes don't affect a working solution.
Description
When a Pull Request is raised, attempt to deploy the source in some known environment, but with unique resources that are destroyed upon success or failure.
This work may depend on #89.
Acceptance Criteria
-
run linter(done already by GitHub Actions)-
run bicep build/validate(done already by GitHub Actions)-
run terraform validate(done already by GitHub Action)- run bicep az deployment what-if (will be done in AzDevOps, go touch a subscription and a cloud see if a deployment is possible)
- run terraform plan (will be done in AzDevOps, go touch a subscription and a cloud see if a deployment is possible)
The text was updated successfully, but these errors were encountered: