.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
Sharing Config Data
Understand this important concept to simplify your config.
One of our seven core principles is to keep your config DRY. CloudTruth provides flexible methods and workflows to share secrets, parameters and templates across projects and environments.
CloudTruth's powerful Dynamic Value parameter type allows you to reference and interpolate other values and templates from any project.
Benefits include:
- Reference one parameter from another to build more complex values.
- An example is a database hostname, port, and URL value. With interpolation, the value can be constructed with individual settings. So if the port number changes, the new value only needs to change in one location, and all the references will automatically inherit the new value.
- Reference parameters from another project.
- Cherry-pick parameters to be shared or inherit all the values.
- Implicit values allow config data to adjust according to context, avoiding creating too many variants which become difficult to manage at scale. Use implicit values for:
- Ephemeral environments
- Topic branches
Share parameters and secrets across projects from a common base project. Project inheritance works with interpolation.
Benefits include:
- Most config data can be organized to share a default value across projects. You don't lose anything by sharing since values can always be overridden for exceptional cases.
- Supports templates as well as parameters and secrets.
Environment inheritance allows sharing of config data across environments without repeating values. It's a core concept for DRY config.
Benefits include:
- Set sane default values that can be inherited or easily overridden.
- Secret rotation is easier because the secret only has to be changed in one location and will be reflected in all referenced values.
Last modified 4mo ago