These are the release notes for Apigee Edge Microgateway versions 2.3.x
Some previous versions of Edge Microgateway let you install the software by downloading a ZIP file. These ZIP files are no longer supported. To install Edge Microgateway, you must use:
npm install -g edgemicro
Refer to the installation topic for more details.
Following are the new features and enhancements for this release:
Zero-downtime reload feature
After making a configuration change to Edge Microgateway, you can load the configuration
without dropping any messages. With this change, Edge Microgateway always starts in cluster mode,
--cluster option has been removed from the
In addition, three new CLI commands have been added:
edgemicro status- Checks to see if the Edge Microgateway is running or not.
edgemicro stop- Stops the Edge Microgateway cluster.
edgemicro reload- Reloads the Edge Microgateway configuration with no downtime.
Added version information to CLI
--version flag was added to the CLI. To get the current version of Edge
New Edge Microgateway server SSL options
Edge Microgateway now supports the following server SSL options in addition to
||Path to a
||A string containing the passphrase for the private key or PFX.|
||Path to a file containing a list of trusted certificates in PEM format.|
||A string describing the ciphers to use separated by a ":".|
||If true, the server certificate is verified against the list of supplied CAs. If verification fails, an error is returned.|
||The SSL method to use. For example, SSLv3_method to force SSL to version 3.|
||The server name for the SNI (Server Name Indication) TLS extension.|
Allow custom API endpoint for configuration
There are new configurable endpoints for the authorization proxy that support the use of a custom auth service. These endpoints are:
For details, see Using a custom auth service.
Send log files to stdout
You can send log data to standard output with a new configuration setting:
edgemicro: logging: to_console: true
See Managing log files.