We’re excited to announce the release of Inmanta Service Orchestrator 6.1, which includes a range of new features and improvements. Here are some of the highlights:
- Metrics dashboard: Gain valuable insights into each environment. Our new metrics dashboard provides detailed information to help you make informed decisions.
- Expert LSM APIs: Our lifecycle service manager (LSM) offers additional APIs that allow you to force actions and override built-in validations and safety checks. This provides you greater control and flexibility when onboarding existing services.
- Module Release Tool: A new tool to simplify the process of releasing new module versions, helping you streamline your release process and get your updates out faster.
- Support Database Export: Our support tool now offers the ability to generate database exports even when pg_dump is not available on the server, giving you more options and greater flexibility in troubleshooting issues.
In addition to these exciting new features, we’ve also updated all of our dependencies to the latest version and fixed a number of issues, ensuring that Inmanta Service Orchestration 6 remains reliable, secure, and up-to-date. Our documentation includes the upgrade instructions as well as the complete changelog.
Every environment now lands on a dashboard with metrics about the current environment. This is a first version of the dashboard, in next versions we will further improve it and add more details.
LSM Expert mode
In this release we introduced three expert mode APIs on Inmanta’s Lifecycle Service Manager (LSM). These APIs allow you to:
- Force a state on an instance,
- Permanently delete an instance from the database,
- Change any parameter in any attribute set.
Each of these operations are only available when you enable the “Expert mode” setting in the environment. These operations also do not trigger any validation or state changes in the service instance.
This API is incredibly powerful, providing users with the ability to bypass all protection and validation measures. However, with great power comes great responsibility – improper use of this API could potentially corrupt a service instance. That being said, there are several valid use cases where this functionality can prove invaluable, including:
- Service onboarding: This API supports the onboarding of new services, allowing users to easily onboard existing services.
- Removing unintended values: In cases where instances have persisted values that should not have been saved (such as sensitive information like secrets), you can use this this API to remove these values.
- One-off procedures: In certain operational scenarios, there is a need for one-off procedures that require to bypass validation measures. This API can support these types of procedures, providing greater flexibility and control in managing your workflows.
The use of this API should be approached with caution, and should only be used in cases where it is absolutely necessary. However, for those who require this level of control, our API can be an incredibly valuable tool. In the next release (ISO 6.2) the frontend will provide a UI for this new functionality.
Module Release Tool
In this release we add the “inmanta module release” command. This command is an upgrade to the existing “inmanta module commit” command, and provides several new features to simplify the module release process.
One of the most significant enhancements is that the “inmanta module release” command now automatically increases the version number to the next development version. This ensures that your module v2 builds always have a higher version than the latest release. This eliminates the need for manual version number changes, reducing the likelihood of errors and streamlining the release process.
To learn more about how the “inmanta module release” command works and how to use it, be sure to check out the documentation. We hope this new feature helps make module release management smoother and more efficient for our users.