In May, we released Resoto 3.5! Resoto 3.5 is chock-full of new features and essential bug fixes—we merged 50 pull requests.
Ever wished you could travel back in time to see what your cloud infrastructure looked like a week, a month, or even some years ago? Now you can!
Resoto Rewind automatically takes snapshots of your cloud infrastructure, allowing you to observe its historical state.
This feature helps you gauge, for instance, compliance improvement with new tagging policies. It also assists in making better decisions when purchasing reserved instances by revealing how your compute demand has fluctuated over time. Resoto Rewind supports all cloud providers we cater to and is automatically enabled.
Resoto Infrastructure Apps
Resoto offers help with a variety of tasks, from tag correction to resource cleanup. Until now, if you desired to implement infrastructure logic that Resoto didn't support natively, you'd have to compose a custom plugin in Python. But with Resoto Infrastructure Apps, we're introducing a low-code method of implementing infrastructure logic.
Infrastructure Apps are Jinja templates, which many will recognize from systems like dbt. They're inherently secure because they can not execute code themselves; instead, they generate Resoto commands for execution. This allows for dry-run and audit of the commands prior to execution.
Previously, Resoto used a pre-shared key to authenticate with the system and establish trust between components. With Resoto 3.5, we're introducing Resoto Identity. This new OIDC-like service enables you to create and manage users and their system access.
Consequently, the first time you open Resoto UI or Resoto Shell after upgrading to Resoto 3.5, the system will prompt you to create a new user. The system currently only supports the "admin" role, but we plan to add more roles and the ability to connect third-party OIDC and SAML2 providers in the future.
New Google Cloud Collector
After months of meticulous testing, we're excited to release our new Google Cloud collector.
It not only supports more Google Cloud resources than the former collector but also ensures that all resources now contain a complete set of Google Cloud metadata.
- For K8S Ingress and DigitalOcean, load balancers now correctly display the list of backend servers in the unified data model.
- A bug in the DigitalOcean collector that caused the collector to fail for old snapshots lacking a region association has been fixed.
- AWS EBS volumes now consistently have
- Configuration files written to the home directory now have
write_files_to_home_dir, paths are now recursively created if they don't already exist.
We hope you're as thrilled with these updates as we are. As always, your feedback is invaluable to us, so don't hesitate to share your thoughts on these new features and improvements.