We recently released version 4.2.0 of the Inmanta Service Orchestrator product. In this article we highlight some of the notable new features since release 3.4.0 (e.g. improved service inventory view). The full changelog of the Inmanta Service Orchestrator release is available in our documentation with all improvements, new features and bugfixes.
Improved service inventory view
The service inventory received a complete overhaul. It now provides a better overview of all the instances and their current state. Use sorting on the columns and filtering on state, attribute sets and so on, for an improved overview and troubleshooting.
The details of each service instance gives you conveniently access to details, attribute sets (including deeply nested trees), state history, events, resources and lifecycle state configuration.
The new Inmanta Service Orchestrator release also allows you to use labels on your lifecycle states to tightly control how the state of each service is presented in the service inventory.
Each label matches with a color and icon in the console:
Customize service identity
Up till now the ID of a service instance was always based on the internal UUID. In this release it is possible to mark an attribute as the identifying attribute.
In the web console the ID column will be replaced by the attribute marked in the entity binding.
This attribute can now also be used to fetch a service instance through the API instead of having to use the UUID-based ID of the instance.
Filtering and sorting
Most of the API endpoints in the service inventory now have searching and filtering capabilities. You can get the details from the documentation or the built-in OpenAPI documentation.
Broader OS, Python and PostgreSQL support
Inmanta still recommends Python 3.6, PostgreSQL 10 for this release. We have official RPMs for both RHEL 7 and RHEL 8. For testing and development you can also use Python 3.8 and PostgreSQL 11 or 12. The official RPMs are still the only distribution on which you can get 24/7 premium support.
Experimental compiler caching
The compiler can now cache compiled model files. This will speed up compilation, especially with large service models. To enable caching on the compiler, either set the config value
compiler.cache in the
.inmanta file or pass the option