Scalr

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.

Ryan Fee

• 2 min read

In April, we rolled out new features aimed at improving flexibility in how teams manage state and workflows, enabling cross-environment operations, and expanding policy and GitOps capabilities.

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.

Screenshot of an example of Storage Profiles in Scalr screeshot
Example of Storage Profiles in Scalr

Cross-Environment Run Triggers and State Sharing

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.

Screenshot of a example of Scalr’s Federated Environments
Example of Scalr’s Federated Environments

Pull Request Dashboard

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.

Screenshot of an example of the pull request dashboard in Scalr
Example of the pull request dashboard

API Token Expiration Dates

Administrators can now set expiration dates for API tokens. This enables enforced token rotation policies, improving security without adding manual processes.

New OPA Input: Merge Error Attribute

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 use Scalr to see how we can help you adopt grow and scale Terraform/ OpenTofu at your organization.