Caution
Information in this section refers to a future offering that may not be available at this time. This documentation may also be updated at any time. Please reach out to your Account Manager for more information.
Using GitHub¶
There are three kinds of repositories in the rackspace-infrastructure-automation organization:
Rackspace-wide or Public Projects
Rackspace-wide projects containing documentation and/or reusable code to build Customer infrastructure (Documentation, Terraform modules, etc)
Naming convention: <Cloud Platform or rackspace>-<Tool/Purpose>
Examples: rackspace-documentation, aws-terraform-base_network
Customer shared repository
Customer repositories that are shared across all of a single Customer’s accounts (Reusable Terraform artifacts)
Naming convention: <Customer number>-<cloud provider>-<Human Readable, arbitrary name>
Examples: 12345-aws-Customer1, 67890-aws-Customer2, etc|
Customer account-level repository
Customer repositories specific to a cloud account (code used to directly build AWS, GCP, Azure, etc account resources)
Naming convention: <Customer number>-<cloud provider>-<cloud provider account id>-<Human Readable, arbitrary name>
Examples: 12345-aws-45378692529-Customer1, 67890-aws-9085432530-Customer2, etc|
Branches & forks¶
- All repositories should have a README.md committed to master
- master branch is protected, only controlled by CI/CD. master should always reflect a sane, valid, current state
- Short-lived branches will be used for changes
- Forks won’t build using our CI/CD system, by design
- Releases will exist as a tag, and will be created using the GitHub releases mechanism.
Membership and collaboration¶
- Racker accounts will be added & removed to the Rackspace team, automatically.
- Rackspace will automate adding and removing members & outside collaborators. We anticipate additional work around Identity and Identity federation in the future.
- Rackers will be added to specific teams based on which level of access and which cloud providers they work with.
- Customers must request GitHub users be added or removed from their repositories, and will only be serviced during US or UK Rackspace business hours.