2.0.0
Pulsar Admin Console 2.0.0 Released
This release refactors the Pulsar Admin Console to remove the dependency on nginx as well as the Burnell component by embedding the functionality of those components within the Admin Console server. This simplifies the installation of the Admin Console, with the only external dependency being node.js.
This release also restructure how config files are handled. There is now a single directly for all configuration files (./config). The default configuration is in default.json. Settings can be overridden by placing a local.json file in the directory with just the settings that are to be updated. Configurations from previously versions of the Admin Console are NOT backwards compatible will have to be updated.
This release also enhances the documentation, providing details about each available configuration option.
What's Changed
- Replace localshost with localhost by @michaeljmarshall in #53
- Updates for easier dev setup by @mfortman11 in #54
- Added Standalone pulsar to docker-compose for dev by @NadirJ in #55
- Configure Node server to forward requests to Pulsar by @mfortman11 in #56
- Update load-report call by @mfortman11 in #57
- Load report cleanup by @mfortman11 in #58
- handle multiple redirects by @mfortman11 in #59
- Config refactor by @cdbartholomew in #60
New Contributors
- @mfortman11 made their first contribution in #54
- @NadirJ made their first contribution in #55
Full Changelog: 1.2.9...2.0.0
Artifacts
Docker Image: datastax/pulsar-admin-console:2.0.0
Tarball: Attached to this release here. The tarball contains all necessary node dependencies. We used Node v14.18.3 to build the artifact. Below you can find the sha512 checksum for the tarball:
SHA512(pulsar-admin-console-2.0.0.tar.gz)= 2273a3edb76929121b969d706950993c812a674cf4af03a743cb85672be0355c9c92703d09891206a75dd1b0f1cf71d49a986092e19e0668eb7ebe2d9a61eb55
