Product Updates April 2025: Flexible Storage Options, Federation, and GitOps Workflows
Scalr’s April 2025 release adds flexible storage backends, cross-org federation, and GitOps workflow boosts for faster, safer Terraform automation.
In April we shipped a batch of features around how teams manage state and run workflows. A few of them open up operations across environments, and others extend what you can do with policies and GitOps.
What Are Storage Profiles?
Storage Profiles now support storing state, logs, and configuration files either in Scalr or in customer-managed buckets across AWS, Azure, or GCP. This gives administrators more flexibility and control over data residency, compliance, and cost management, while maintaining Scalr’s automation and governance benefits. More information can be found here.
How Do Cross-Environment Run Triggers and State Sharing Work?
We introduced federated environment access, making it possible for workspaces in different environments to share state and trigger runs across boundaries. Many organizations separate workspaces into different environments for governance or team structure reasons. This update makes it easier to automate workflows across those environments without manual coordination. More information can be found here.
What Does the New Pull Request Dashboard Show?
A new dashboard now displays all pull requests linked to a workspace, along with their statuses. This gives teams better visibility into pending infrastructure changes and reduces the need to switch between tools when reviewing and managing changes.
Can You Set Expiration Dates on API Tokens?
Administrators can now set expiration dates for API tokens. This enables enforced token rotation policies, improving security without adding manual processes.
What Does the New OPA Merge Error Attribute Do?
We added a new merge_error attribute to the policy input, capturing merge blocker statuses (like ‘dirty’, ‘blocked’, or ‘behind’) from GitHub pull requests. This allows teams to proactively enforce policies that prevent runs from executing against pull requests in a blocked or unstable state. An example OPA policy can be found here.
Thanks for getting this far… feel free to sign up and see how Scalr can help you run Terraform and OpenTofu at your organization.