Skip to content
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

Customerize your template for the app team #354

Open
4 tasks
ianphil opened this issue Oct 2, 2019 · 0 comments · May be fixed by #362
Open
4 tasks

Customerize your template for the app team #354

ianphil opened this issue Oct 2, 2019 · 0 comments · May be fixed by #362
Assignees
Labels
documentation Applies to documentation and diagrams effort - small 1 day effort

Comments

@ianphil
Copy link
Contributor

ianphil commented Oct 2, 2019

Description

As a user, I'd like to understand how to share the template/pipeline with app teams so they can start deploying their infrastructure.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

  • Should explain the version and go process as a lab.
  • Should contain the code for application.tf
  • Should contain the code for application.yaml
  • files should be located in the root of the app repo in an infra folder

Also, here are a few points that need to be addressed:

  1. See stub file for this story: docs/6_CUSTOMERIZE_STACK.md

Resources

Epic #346

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

@ianphil ianphil added documentation Applies to documentation and diagrams effort - small 1 day effort labels Oct 2, 2019
@ianphil ianphil added this to Sprint Backlog in Current Iteration via automation Oct 2, 2019
@ianphil ianphil moved this from Sprint Backlog to V1 in Current Iteration Oct 2, 2019
@ianphil ianphil moved this from V1 to Active in Current Iteration Oct 8, 2019
@ianphil ianphil self-assigned this Oct 8, 2019
@TechnicallyWilliams TechnicallyWilliams linked a pull request Jun 27, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Applies to documentation and diagrams effort - small 1 day effort
Projects
Development

Successfully merging a pull request may close this issue.

1 participant