New documentation for the new AWS Organization and the new Terraform 1.0 repositories. Move old AWS and Terraform documentation to "legacy" status (since they are still valid, just not for any new resources).
How does this address that need
rename the aws and terraform .rst files to include "legacy"
create new aws-2.0.md and terraform-1.0.md files
the new aws-2.0 page includes
information about our new AWS Organization
information about the new AWS SSO based sign-in
links to more detailed documentation in the InfraEng Confluence wiki
the new terraform-1.0 page includes
information about our new Terraform repository model
information about our Git flow (vs GitHub flow) approach to our Terraform repos
information about our automated management of repos
information about our Terraform Cloud Organization
links to more detailed documentation in the InfraEng Confluence wiki
Other Notes
I'm looking for feedback from InfraEng that the information being added to our DevDocs accurately represents our new approach to AWS, Terraform, and infrastructure.
I'm looking for feedback from EngX that the information about access to AWS and the notes about our approach to managing branches in our repositories makes sense.
Why are these changes being introduced
New documentation for the new AWS Organization and the new Terraform 1.0 repositories. Move old AWS and Terraform documentation to "legacy" status (since they are still valid, just not for any new resources).
How does this address that need
.rstfiles to include "legacy"aws-2.0.mdandterraform-1.0.mdfilesOther Notes
I'm looking for feedback from InfraEng that the information being added to our DevDocs accurately represents our new approach to AWS, Terraform, and infrastructure.
I'm looking for feedback from EngX that the information about access to AWS and the notes about our approach to managing branches in our repositories makes sense.