Best practice for multi org and multi env deployment

We have 2 orgs as of now org-test and org-prod. whats the best way to promote APIs from org-test --> org-prod in automated way. I know api can be downloaded as a zip file and imported in other org using Apigee edge ui. Also i have seen the link here which have script to download.

Whats the best way to promot apis from non prod org to prod org in a automated (Non UI) way?

1 1 284
1 REPLY 1

The best way is to do that through your automated CI/CD pipeline, and use a script or program.

Ideally the script should

  • read configurations for API Proxies and other assets (sharedflows, virtual hosts, target servers, KVMs, truststores, caches, and so on) from your source-code control repository
  • import them into the org in question, or create them (as appropriate)
  • deploy the proxies and sharedflows to an environment
  • run tests
  • report results
  • and maybe automagically promote to production if all the tests succeed

This is what many of our customers with mature devops practices do. They rely on tools built in JavaScript or Golang or bash, using the various libraries and wrappers out there on github.

If you need help with this kind of stuff, you can ask for guidance from a Customer Success representative. Our team has helped lots of customers integrate Apigee Edge into their Continuous Integration / Continuous Deployment systems.

Get in touch with your salesrep to arrange that help.