3 ms·
So long as you are systemically protecting against someone spinning up a QA instance against some Prod resource then it’s probably alright to ship most config w
by CraigJPerry 3y ago
So long as you are systemically protecting against someone spinning up a QA instance against some Prod resource then it’s probably alright to ship most config with the app. You don’t want to allow a (entirely predictable) human error to cause 100k auth denied retries against a prod job submission queue from QA for example. Much config isn’t about infra though, it’s often what kind of ResolverStrategy (made up but plausible sounding name) bean do I want to wire in each env for example.