Revisit cloudformation template bootstrap process
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
It seems the cloudformation template is both generated in github and ends up as a build artifact and also can be generated and run locally with a just command. When it's generated it has a default set of TrustedPrincipals in it, which works for a brand new stack, but for applying to an existing stack to update, it will not use the new default values in the template and must be done manually.
We should revisit this to see if there's a better way, or if a cloudformation stack is even the correct route here. It's partially manual which is obviously not ideal, and also not documented anywhere I can find so at the bare minimum we need to document the correct process.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CloudFormation template, its GitHub-generated build artifact, and the just command used for local generation. Trace how TrustedPrincipals defaults are applied to new versus existing stacks. Done should include a decided bootstrap or update process and documentation of the correct commands and manual steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100