Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    The configuration is shipped as part of the product. This is an in-house so the customer is, essentially, the same entity as the solution provider. What other audited mechanism is available for configuration changes shipped as part of the application? Or, put another way, if the configuration happened to be in the same release as a code change I bet everyone would be OK with the code version number change "carrying" the config change with it. Commented Dec 8, 2016 at 19:11
  • @thehowler Audited, and for just one customer who is also the provider? A simple VCS commit? Commented Dec 8, 2016 at 19:43
  • 1
    There is a huge difference between a customer changing a config value and the default value of a distribution changing. -1 Commented Dec 9, 2016 at 0:22