I was just wondering if someone from Octopus could give their thoughts on how they are thinking about configuration management going forward. As our deployments get more complicated and involved, and as Octopus is adding features like multi-tenancy, management of the different variables is getting unwieldy. Add to this our use of config transforms, and the picture gets even more confusing. While we love Octopus, it seems that configuration management is one of the major missing pieces from the software (either intentionally or not). Are there any plans to tackle this area inside the Octopus software?
Just to clarify, I am thinking along the lines of things like:
Configuration Versioning (checkins, who changed what why, etc.)
Easier management of variables (scoping is currently a nightmare with somewhat complicated environments)
Recommendation on whether to store configs in source control and pass them to Octopus, or store them in Octopus directly
Please let me know what you guys are thinking about along these lines, or if it’s completely missing from your radar. Thanks!