-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add stubs for adding multiple AWS accounts. #1120
base: master
Are you sure you want to change the base?
Conversation
* Add account vending documentation --------- Co-authored-by: Eben Eliason <[email protected]> Co-authored-by: Eben Eliason <[email protected]>
* Add docs for Pipelines to DevOps foundations * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * Update _docs-sources/foundations/ci-cd/pipelines.md Co-authored-by: Eben Eliason <[email protected]> * address PR feedback --------- Co-authored-by: Eben Eliason <[email protected]>
* Add manage accounts page --------- Co-authored-by: Andrew Ellison <[email protected]>
* add module default docs --------- Co-authored-by: Eben Eliason <[email protected]>
* Add docs for folder structure to tf foundations --------- Co-authored-by: Eben Eliason <[email protected]>
* initial docs for enabling control tower * fix root thing * add next steps * Add more detailed step-by-step * Add prerequisites and reformat steps * address pr comments * Add Instructions for Shared Account Permissions
If your organization has a need for more than one `infrastructure-live` repository, there are two primary approaches to adding Pipelines support to additional repositories: | ||
|
||
1. Create a new `infrastructure-pipelines` repository (though named something different) for the new `infrastructure-live` repository | ||
1. Use a single `infrastructure-pipelines` repository for multiple `infrastructure-live` repositories. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not currently supported. We have a story this sprint to determine how to best accomplish this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification, and understood.
It turns out that the ability to support multiple infra-live repos for one pipelines repo is part of CORE-1274, whose A/C include docs, so we'll leave this open to be covered by that story. |
Many users will have the need to set up Pipelines for more than one
infrastructure-live
repo, so we should address explicitly how users can do this.Regarding priority, I'm not sure where this fits, but I would expects users to ask about it in the next few days, possibly as soon as Wednesday.