your configuration data is stored in different sources (git, proprietary, CMDBs ...) and formats (yaml, xml, json, ini ...). Nobody /nothing has the "full picture" of all settings for a given application in a given environment at a given moment in time
understand what has changed takes a lot of time & effort
figuring out what changed on infra, environment and application settings between any 2 moments in time (diff between "right now" when we have an issue, and 1 week ago when there was no issue) takes hours with several people involved
no impact analysis
when somebody or some tool changes some config data setting, nothing calculates the full impact of the change(s). You rely on expert users to manually assess the impact and try to prevent errors are happening
no automated validation
there are no automated policies in place which validate that all technical, functional and compliance rules are still OK when the config data changes will be applied.
audit trail, security, RBAC
you are struggling to keep track of who has changed what, who is allowed to view/change what and to ensure that sensitive data (passwords, tokens, API keys ...) is encrypted and for authorized eyes only.
interested to see how SWEAGLE automates config data management?