Currently, a user must use the UI or CLI to construct their architecture (by creating stacks and blocks).
In addition, a user could define this structure through code checked into a repository.
This enables engineering teams to review changes to infrastructure through PR.
How will it work?
Users define their blocks in one, or many code files checked into a repository.
These users connect a repository to construct and track any changes made to the definitions automatically.
Any blocks created through this flow will not be editable through the UI, but instead only through changes to the code.
If following a microservices pattern where each repo is an app, the infra code should be able to stand up resources independently.
Open Questions
[ ] What file format is desirable? yaml, hcl, json
[ ] How should shared resources be handled across infra code files/repos?
Overview
Currently, a user must use the UI or CLI to construct their architecture (by creating stacks and blocks). In addition, a user could define this structure through code checked into a repository. This enables engineering teams to review changes to infrastructure through PR.
How will it work?
Users define their blocks in one, or many code files checked into a repository. These users connect a repository to construct and track any changes made to the definitions automatically. Any blocks created through this flow will not be editable through the UI, but instead only through changes to the code.
If following a microservices pattern where each repo is an app, the infra code should be able to stand up resources independently.
Open Questions