edgemicro start returns with exit code 0 even when key and secret are incorrect

Google Cloud Apigee
1

I changed the org and env that microgateway was pointing to on a machine but forgot to update the key and secret. Upstart happily thinks that process is still running because edgemicro start returned with exit code 0 even though it seems to have exited in error based on the logs:

cache configuration /home/vagrant/.edgemicro/demo-****-test-cache-config.yaml does not exist. exiting.
info: products download from [https://demo-****-test.apigee.net/edgemicro-auth/products](https://demo-****-test.apigee.net/edgemicro-auth/products) returned 200 OK
warning: config download from [https://edgemicroservices-us-east-1.apigee.net/edgemicro/bootstrap/organization/demo-****/environment/test](https://edgemicroservices-us-east-1.apigee.net/edgemicro/bootstrap/organization/demo-****/environment/test) returned 401 Unauthorized

Is it correct for the process to be exiting with code 0 in this situation?

2

Hi there,

You’re correct. This is a bug. I submitted a Pull Request you can track here: https://github.com/apigee-internal/microgateway/pull/44

Thanks, David!

3

@David Teirney

The fix for this has been merged and published with edgemicro@2.0.11.

Here are the complete release notes: https://github.com/apigee-internal/microgateway/releases/tag/v2.0.11