In order to make the best use of our CI process, we would like to build API Proxy artifacts (zip files) that are _consistent_ across the environments (dev, test, prod). i.e. Build once, deploy to multiple environments. So rather than have build-time replacement of xml elements in the API proxy files, we would just follow a best-practice of ensuring that *all* environment-specific configuration is stored in either Target Server, KVM, or Vault. Does this sound like a reasonable approach?
This is what we have done for all of our java artifacts (jars, wars, ears, etc.) in the past and it has worked well.
LinkedIn
Twitter
