I have a question about defining datasource configurations for different environments. I know there's a way to use system configurations to set which datasource configuration is the 'default' for an environment. But can you also prevent a specific datasource configuration from being used?
For example, if I create a dev/qa/prod config for my datasource, so that I don't have to edit anything as I migrate through the instances, is there any way to prevent someone from using the prod config while working in dev?
I've been doing alot of reading about ways to do migrations with Data Services, and several blogs mention using datasource configurations for datasources, but I couldn't find any that addressed this specific issue. I like the idea of the ease of the datasource configuration method, but I'm just concerned about the security aspect of having that production configuration hanging out in development and available for anyone to use. It seems like it wouldn't be that hard to accidentally nudge that drop down box when you're running a job and end up using the wrong configuration, and thus running against the wrong environment.