While I don't know your deployment topology (distributed deployment or not, or even if you have multiple deployment servers)...
If you have multiple deployment servers, there is a so-called Multi-tenant scenario "Example: How to propagate apps from Primary to Secondary Deployment Server" http://wiki.splunk.com/Deploy:DeploymentServer (which will be unsupported in the next major release of Splunk 7.0). More details straight from the docs: http://docs.splunk.com/Documentation/Splunk/6.2.3/admin/Tenantsconf. There is another Answers post on this method: http://answers.splunk.com/answers/60559/can-one-deployment-server-send-data-to-another-deployemnt-server.html
If you version control your apps in say Git (or some other version control system), you can check in your config apps which live on say on DS1 (deployment server one for DEV/UAT), then you can pull down your config apps on DS2 (deployment server two for ITA, etc.), then reload the deployment server.
In a distributed deployment, which most large enterprise environments have due to having data collected from multiple data centers, method 2 might be your best bet!
Good luck!
... View more