Release Notes v0.97
Release v0.97 brings your own GCP Secret Manager for environment secrets for SaaS customers, variable history with change tracking in release preview, effective config across the console, GitLab and Bitbucket for module repositories, and release briefs alongside Praxis.
✨ What's New
Variable History and Change Tracking
Facets now keeps a history of each environment's variables and secrets: who changed what, when, and which release used which version. When a variable or secret changes, every resource that references it is marked pending in the release preview, so a value change no longer goes out with the next release unnoticed. Secret values are never stored in history. Facets only records whether a value changed, never the value itself.
(Early Access) Your Own GCP Secret Manager for Environment Secrets (Only for SaaS)
On Facets SaaS, environment secrets can now live in GCP Secret Manager in your own GCP project. Pick the store from the new Secret Store dropdown in Environment Settings. For GCP, choose Automatic, User-managed or Regional replication. Once an environment moves to your store, every read and write for it goes there, and releases pick up values from it. Ask Facets support to enable it for your control plane.
Effective Config Across the Console
The Overrides page, launch wizard, release preview and release details now all work from the effective config: your blueprint and overrides, merged. A resource shows as pending only when the config the next release would deploy actually differs from what was last deployed, and past releases show a before-and-after diff of what changed.
GitLab and Bitbucket for Module Repositories
Module repositories are no longer GitHub-only. Set them up on GitLab or Bitbucket and get the same flow you have on GitHub: repository setup, module sync, and pull requests.
Release Briefs
Failed Releases triggered through Praxis now come with an AI-generated summary. In the UI, it also shows a Release brief button, grouped with Praxis. The brief tells you what the release set out to do and what happened, so the next person or agent that looks at the release starts with that context.
📈 Enhancements
- History, One Row per Change: The History tab now shows one row per change, with table and timeline views, the full config details, and the blueprint commit behind each change.
- Say Why You Acted: Add an optional reason when you destroy an environment, unlock, approve, reject, sign off or pause a release. Users and user groups can now carry descriptions too (through Praxis for now and coming to the UI soon).
- Plan Without Apply on Staged Releases: Users who have plan permission can now start staged releases. Applying them still needs apply permission.
- No More 64 KB Cap on Environment Secrets: Large sets of environment secrets are split across multiple secrets automatically, so you can keep adding secrets past the AWS Secrets Manager size limit.
- Leaner New AWS Environments: New AWS environments no longer enable the EKS EFS CSI add-on by default.
- Tighter Security: Error responses no longer expose internal exception details, and secret values and Git tokens are no longer written to logs.