Outstanding Todos:

[cellistigs]

Prioiritize these todos and link them to existing issues:

• Contrib:
  • make blueprint simpler, update the stack name automatically.
• Blueprint
  • AMI, other blueprint parameters to cfn parameters for faster updates.
• Monitoring lambdas:
  • if tag info exists, pass that to me or the user when things fail.
• Budget
  • In the wild tests for new budget tools with test-tags-bucket stack.
  • autodelete old volumes
• Existing stacks:
  • Move over all existing stacks through PR workflow (after blueprint update, for faster updates overall. )
• Workflow:
  • Build out testing command (#test:****) to deploy a test workflow
• Docker:
  • Integrate docker.
• Users
  • migrate to cognito.

[cellistigs]

Week 1:

• Budget
  • In the wild tests for new budget tools with test-tags-bucket stack.
  • autodelete old volumes
• Monitoring lambdas:
  • if tag info exists, pass that to me or the user when things fail.

Week 2:

• Contrib:
  • make blueprint simpler, update the stack name automatically.
• Blueprint
  • AMI, other blueprint parameters to cfn parameters for faster updates.

Week 3:

• Workflow:
  • Build out testing command (#test:****) to deploy a test workflow
• Existing stacks:
  • Move over all existing stacks through PR workflow (after blueprint update, for faster updates overall. )

Week 4-6

• Docker:
  • Integrate docker.

Need help:

• Users
  • migrate to cognito.

[cellistigs]

Week 1:
How do we automate tests?

• for the large majority of stacks, we can do this by assuming that we don't require particular fields for the input and output. Just create a couple of files called submit.json and config.yaml, where config.yaml has a duration parameter.
• these can be included in the test resources.
• when a test stack gets deployed with some users, we can get the user group name, and write these resources to that user.
• you can get instance names with certificate parsing.
• you can use instance names to assure that one deployment works successfully.

[cellistigs]

We can hook this automation into the prtest.yaml file that is in the security_upgrade branch.

[cellistigs]

Week 1:

• Budget
  • In the wild tests for new budget tools with test-tags-bucket stack.
  • autodelete old volumes
• Monitoring lambdas:
  • Review and new features
  • if tag info exists, pass that to me or the user when things fail.

Week 2:

• Contrib:
  • make blueprint simpler, update the stack name automatically.
• Blueprint
  • AMI, other blueprint parameters to cfn parameters for faster updates.

Week 3:

• Workflow:
  • Build out testing command (#test:****) to deploy a test workflow
• Existing stacks:
  • Move over all existing stacks through PR workflow (after blueprint update, for faster updates overall. )

Need help:

• Docker:
  • Integrate docker (Set up meeting with Ian and Monadical)
• Users
  • migrate to cognito.