Cascading Configuration Files

The various cumulusci.yml files cascade over each other to form a final version which consumed by cci in order to know how specific pieces of automation should be executed.

flowchart TD;
   A>final cumulusci.yml]
   B(universal cumulusci.yml) --> A
   C(global cumulusci.yml)-- overrides --> B
   D(project cumulusci.yml)-- overrides --> C
   E(local project cumulusci.yml)-- overrides --> D

   classDef configFile fill:#028DA9
   class A,B,C,D,E configFile

   F[Defines the standard tasks and flows, not editable] --- B
   G[Configure changes that occur across all CumulusCI projects on your computer] --- C
   H[Configure changes that can be shared with users across the project] --- D
   I[Configure changes to the project that are just for you] --- E

   classDef description fill:#067701
   class F,G,H,I description