This is a small release primarily focused around documentation and some minor quality-of-life bug fixes.
- The controller name is now rendered in the model lists.
- The machine table in the model details pages now shows the Juju agent status values instead of the provider instance status.
- The pinger now stops pinging if the websocket connection is terminated.
- The charts on the controller page now show as disabled if no data is provided.
- When filtering the tables in the model details pages the unit counts no longer incorrectly change.
- When logging out it now shows the log-in UI again.
- Local charm icons are now shown as the default charm icon instead of broken. We’re working with the Juju team on displaying the correct charm icons and this will be available in a future Juju release.
- Updated Sentry ID to allow for better issue tracking.
- Added how to perform a release.
- Added how to write React components.
- Added how to write tests.
- Added instructions on QA.
- Added the Juju commands.
- Added instructions on accessing the Dashboard via nested VMs.
Over the past month we’ve been focused on a few things that you’ll see in upcoming releases.
- Investigations into:
- Adding the ability to position applications in the Topology to better represent your models. These positions will be persisted and included with bundle exports so future deployments of the bundle will retain the same visualizations.