Blame docs/ansible/topology.md

6f32ae
# Ansible Environments
6f32ae
6d98f4
As explained in the [Overview](../index.md#available-environments), we use different ansible inventories based on the target infra that we'll target.
6f32ae
6f32ae
Apart from the roles and playbooks which are all common for *all* environments, each env will use its own :
6f32ae
6f32ae
  * inventory
6f32ae
  * filestore
6f32ae
  * pkistore (shared though for `main`, `stg` and `dev`, but different for the other ones)
6f32ae
6f32ae
Based on the requirements and on which git forge solution it's hosted on, people will be granted RWC (Read / Write / Commit) rights on the specific (non public, for obvious reasons) git repositories
6f32ae
6f32ae
Worth also knowing that, depending on the Env requirements, some will be fully encrypted (with `git-crypt`) and other will have a mix of readable/encrypted content (with `ansible-vault`) so that (even if private repositories), some other team members can submit PR/MR against inventory without having access to the stored (and encrypted) credentials