Any best practices to manage microgateway changes and deployments?

Google Cloud Apigee
1

Looking for strategies to manage changes and deployment to servers. Changes include:

  1. Customizations to edgemicro-auth to support password grant and other extensions
  2. Org / Env configurations for plugins, etc.
  3. Custom plugins

For edgemicro-auth changes I can just treat it as a typical proxy and use existing CI/CD tools.

For Org / Env configurations, its merely distributing the yaml files and keys/certificates.

For custom plugins, I think they need to be located in: {installdir}/lib/node_modules/edgemicro/plugins as the dir option doesn’t seem to accept a full path. Therefore, the custom plugin folders need to be distributed as well.

How are people addressing this?

2
  • @Miren on setting up local npm repo for micro gw mgmt