I’m looking at source controlled key/value storage of configuration data/variables. I want this to be held in source control (Git) as the single source of truth. This can then be shared to a number of services via Consul using its API. My idea is to to then pull in variable/configuration data at run-time from Consul to scripts called by Octopus Deploy.
Has anyone attempted anything like this and has it working or any suggested alternatives?
This is a proposed alternative to using stored variables in Octopus because they are not source controlled. I want scripts, variables, everything stored in our source of truth (Git). I also want all configuration in a YAML type format which can be interpreted by multiple tools within an entire deployment pipeline (including provisioning).
Relates to a couple of user voice submissions: