|
|
|
|
|
by gregmac
1060 days ago
|
|
> Some aspects of the business want to tweak things and it should be reasonably guaranteed that the automated side never touches it. What would a legitimate case for this be? It seems to me like any changes either must be done via IAC -- and tracked in source control, PR'd, tested in non-prod, etc -- or a missing feature. If there's a legitimate case for modifying something not in IAC, it should be supported -- this is what I mean by "missing feature". The app and/or IAC should have code for that feature. Modifying IAC-deployed settings is akin to someone hacking the binary of an executable from a software vendor while still expecting the vendor to support that modified executable. Not gonna happen. |
|