---
# System prepended metadata

title: SOP for aligning tower dummy credential repos

---

# SOP for aligning tower dummy credential repos
The aim of this sop is to out line to the different teams how to align the tower credentials.
Repos that are affected by this sop are: spellgg 

- Config Repo: [https://github.com/integr8ly/ansible-tower-configuration](https://github.com/integr8ly/ansible-tower-configuration)
- Dummy Repo: [https://github.com/integr8ly/tower_dummy_credentials](https://github.com/integr8ly/tower_dummy_credentials)


For each release, a release tag will be create in ansible tower configuration repo and the tower dummy credentials repo.

## Align teams repos
This task is the same for all the teams.

1. Cleandown teams tower instance as per [https://github.com/RHCloudServices/integreatly-help/blob/master/sops/tower_cleandown_process.md](https://github.com/RHCloudServices/integreatly-help/blob/master/sops/tower_cleandown_process.md)
2. Update teams credentials repository and create associated release tag as per [https://github.com/integr8ly/tower_dummy_credentials#updating-private-credential-repositories](https://github.com/integr8ly/tower_dummy_credentials#updating-private-credential-repositories)
3. Bootstrap teams tower instance as per [https://github.com/RHCloudServices/integreatly-help/blob/master/sops/tower_bootstrap_process.md](https://github.com/RHCloudServices/integreatly-help/blob/master/sops/tower_bootstrap_process.md)


## Points that I am on sure about
- Where should this document live?
  - It needs to be a common place that all team would look.
- How do the teams report back changes?
  - If the there is a tag on the master branch this would need to point to the new comments.
  - Do teams need to be watching these repo's all the time. 
  I feel that SRE may need to add something after a release is done.
  This may not get picked up QE or ENG when dealing with upgrades.
- Are these configs get tested / checked for changes during a release upgrade cycle?
  - If not, should these be checked?
  - Is there a sop that is been used during the upgrade that outlines how check these changes?
- Lets say SRE adds a new verible or template which gets pushed back into dummy credentials repo. What ever has to happen with tags gets done.
  - How does QE get informed of the updates to the repo?
  - How does QE apply these new changes to an existing release tag that they may have?
  I am not sure how this process is meant to work.
  Do I have to add all the values bcak in if I am updating an existing tag in cloned copy of the dummy repo.
- How does a team know what is specfic to other teams?
  - What are the chance that one team adds a veriable that conflicts with a different teams requirements?
  - Is there a way of marking what variables are for?
  - Could two teams be adding the same variables with different names?
- Does SRE create mutlply clones of the dummy credentials repo?
  - Example does each customer get their own repo?
  - Is it possible that some setting would be required in only one case? If so these would also need to go back into the dummy credentials repo.
- How do we remove items for the repo?
  - Does the sync function allow or check for the removing of veraibles?
  - How likly is some thing like that to happen?
- How does this affect upgrades?
- If there are templates add by SRE.Which are not required by QE.
  - Does the bootstrap phase require all the details for them templates to be filled in?
  - Or does the bootstrap phase just igorne templates with missing information?
  - If the templates are igonred could that lead to other issues?

