Has anybody come up with any automated solution for disabling remote site settings after a sandbox is created or refreshed?
I'm trying to prevent situations where someone creates a developer sandbox from production and there's still apex code/scheduled jobs in that sandbox that may now try to connect to production services/integration endpoints.
It would be nice if all remote site settings were disabled by default after a sandbox was created/refreshed forcing the user to enable the ones (or creating new ones for test endpoints) that are needed in the sandbox.
I suppose it may be possible using the SandboxPostCopy interface and a custom apex class that uses the Metadata API wrapper https://github.com/financialforcedev/apex-mdapi but I'd like to avoid the going to those lengths if possible.