New Feature: Private Module Registry Namespaces
Private module registry namespaces allow you to organize Terraform and OpenTofu modules easier and select which environments to share them with.
For years, Scalr has provided a robust private module registry, helping organizations standardize their Terraform and OpenTofu module consumption. Previously, the module registries were housed either in the account or environment scope, which offered a solid foundation. But as your IaC adoption grows, so does the need for more granular organization and flexible sharing. That's precisely what module namespaces deliver.
What are Module Registry Namespaces?
Think of namespaces as dedicated, top-level registries for your modules within your Scalr account. They introduce a powerful new layer of organization, allowing you to logically group modules based on teams, projects, departments, or any criteria that align with your organizational structure. You are no longer limited to making the registries only at the account scope or within the environment. You can now create namespaces and assign them to the entire account or select environments.
What's Different from the Old Module Registry Concept?
Previously, modules could only be published directly to either the account scope (making them available to all environments and workspaces) or within a specific environment scope (limiting them to that environment). While this worked, it lacked the flexibility needed for larger, more complex organizations.
With namespaces, you now get the following:
- Centralized Namespace Creation: Namespaces are now only created at the account scope. This establishes a clear, top-level organizational layer for all your modules.
- Flexible Sharing, Not Just Scope: Instead of a module being strictly account-wide or environment-specific by its creation location, a namespace owner can now choose to share the namespace with all environments or select environments. This provides far more granular control over module visibility and access.
- Namespace Ownership: Optionally, namespaces can have team ownership assigned to them, and only that team will be able to manage them.
Existing Module Registries
We've ensured a seamless transition. All your existing module URLs remain fully functional after the migration to namespaces. Any existing module calls using the previous account or environment scope will continue to work without changes. Your current IaC workflows will not be disrupted.
Get Started Today!
The new module registry namespaces are available now in all Scalr accounts. We encourage all users to explore this powerful new feature and leverage it to enhance your module management strategy.
For a guide on how to create, manage, and utilize these new namespaces, please refer to our updated documentation: https://docs.scalr.io/docs/private-module-registry
We believe this enhancement will significantly improve your experience with Scalr's private module registry, making it easier than ever to manage, share, and govern your Terraform and OpenTofu modules at scale.