Hi all,
One thing that kept costing me time with Apigee was promoting configuration and API artifacts between environments, especially because OPDK and SaaS behave differently (KVM updates are a good example).
I have open-sourced a small Python tool that handles this with two files: resource.json describes the resources per environment and org, and whitelist.yml selects what gets deployed in a given run.
It supports proxies, shared flows, KVMs, references, target servers, caches, API products and developer apps on both OPDK and SaaS. Credentials are prompted for and never stored, and encrypted KVM values are redacted in logs.
Repo (MIT licensed): GitHub - kalyanchakri02/apigee-opdk-saas-installer · GitHub
I would really value feedback on three things: which resource types or features you would want next (flow hooks, developers, a dry-run mode?), how you handle promotion today (Maven plugin, apigeecli, custom scripts?), and which OPDK versions or edge cases I should test.
Issues and PRs are very welcome.