Closed awkwardindustries closed 4 years ago
As an advocated pattern owner, I'd like to execute these scripts as part of my build/release pipeline without requiring an external script file in order to allow application repositories to refer via reference without additional dependencies.
Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)
devops/providers/azure-devops/templates/infrastructure/scripts/tf-apply-plan.yml
tf-apply-plan.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-create-workspace.yml
tf-create-workspace.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-destroy.yml
tf-destroy.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-generate-plan.yml
tf-generate-plan.sh
azure-pipeline-build-stage.yml
tf-create-workspace.yml
tf-generate-plan.yml
azure-pipeline-release-stage.yml
tf-apply-plan.yml
tf-destroy.yml
Relates to #298
Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)
Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)
Assignee should break down work into tasks here
Description
As an advocated pattern owner, I'd like to execute these scripts as part of my build/release pipeline without requiring an external script file in order to allow application repositories to refer via reference without additional dependencies.
Acceptance Criteria
Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)
devops/providers/azure-devops/templates/infrastructure/scripts/tf-apply-plan.yml
with inline version oftf-apply-plan.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-create-workspace.yml
with inline version oftf-create-workspace.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-destroy.yml
with inline version oftf-destroy.sh
devops/providers/azure-devops/templates/infrastructure/scripts/tf-generate-plan.yml
with inline version oftf-generate-plan.sh
azure-pipeline-build-stage.yml
to utilize template reference totf-create-workspace.yml
instead oftf-create-workspace.sh
azure-pipeline-build-stage.yml
to utilize template reference totf-generate-plan.yml
instead oftf-generate-plan.sh
azure-pipeline-release-stage.yml
to utilize template reference totf-create-workspace.yml
instead oftf-create-workspace.sh
azure-pipeline-release-stage.yml
to utilize template reference totf-apply-plan.yml
instead oftf-apply-plan.sh
azure-pipeline-release-stage.yml
to utilize template reference totf-destroy.yml
instead oftf-destroy.sh
Resources
Relates to #298
Tasks
Stories are intended to be completed in a single sprint; if task breakdown creates addition work then team should discuss promoting the Story to an Epic. Reference: [Minimal Valuable Slices] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/MinimalSlices.md)
Reference: [How to Write Better Tasks] (http://agilebutpragmatic.blogspot.com/2012/04/splitting-story-into-tasks-how-to-write.html)
Assignee should break down work into tasks here