...
- Set up the organization
- There are unique tokens at the org level that get shared with selected repos. For UC, all repos have access.
- GH_ACTIONS_PAT - associated with Guest EID
- PIP_CONFIG - associated with Guest EID
- CMP_API_TOKEN - in Stache from CMP team
- HARBOR_TOKEN - in Stache from CMP team
- HARBOR_USER - in Stache from CMP team (ours was missing; it was emailed to me)
- I don't think PIP_CONFIG will need repo-level changes, but it can be done at the repo level if needed. (Repo-level stuff supersedes org-level stuff in GitHub)
- There are unique tokens at the org level that get shared with selected repos. For UC, all repos have access.
- Set up the repo
- Set up environments: development, quality, production
- Set up the organization
Your project's files
- Add critical files to the project - some of these will help automate GitHub connecting the repo to other pieces of the CMP machinery. Some of these include:
- .github directory - its contents are critical to GitHub allowing you to run a workflow (deploy) the project. This folder should be in Master to get seen by GitHub, even if you want to deploy a different branch. Adding the directory to Master won't harm Master
- Workflow
- Manifests/environment/properties.yml - this is where you specify the name of the secrets file that will be stored in Rancher, in the RUNTIME_SECRETS
- catalog_info.yml
- Commit and push these changes to github. Remember that the .github directory and contents need to be in Master for things to work automagically
- Add critical files to the project - some of these will help automate GitHub connecting the repo to other pieces of the CMP machinery. Some of these include:
...