Configuration files should be treated like code and follow the same gradual rollout practices. See also: https://sre.google/workbook/canarying-releases/ https

Configuration files should be treated like code and follow the same gradual rollout practices. See also: https://sre.google/workbook/canarying-releases/ https://sre.google/workbook/canarying-releases/ Which starts with "a majority of incidents are triggered by binary or configuration pushes". The stats for config related failures is one link away at https://sre.google/workbook/postmortem-analysis/ https://sre.google/workbook/postmortem-analysis/ Where it says 31% of outages in 2010-2017 are caused by "configuration push".