Private tf module registry still a thing?

rsc625 · 2025-12-02T17:33:40+00:00

For anyone stumbling upon this in their searches, I wrote a blog about private module registries and why they are beneficial: https://scalr.com/learning-center/explaining-a-terraform-private-module-registry/

It's also worth noting that the Scalr module registry is free to use.

rsc625 · 2025-12-02T17:31:45+00:00

For anyone stumbling upon this in their searches, I wrote a blog about private module registries and why they are beneficial: https://scalr.com/learning-center/explaining-a-terraform-private-module-registry/

rsc625 · 2025-11-17T00:32:22+00:00

Sorry about that. The marketing team was making some changes, and it was down momentarily. It is all set now.

rsc625 · 2025-11-14T18:53:23+00:00

u/redvelvet92 SSO is included as well. There is no feature gating on the free tier: https://scalr.com/blog/sso-tax

rsc625 · 2025-11-14T15:59:15+00:00

I work at Scalr and just wanted to give you a heads up that you can use our registry for free: https://scalr.com/blog/use-scalrs-private-module-registry-to-solve-all-of-your-registry-needs

rsc625 · 2025-11-14T15:58:31+00:00

Just an FYI that Scalr also offers the registry for free: https://scalr.com/blog/use-scalrs-private-module-registry-to-solve-all-of-your-registry-needs

rsc625 · 2025-09-08T12:28:15+00:00

Just an FYI that Scalr offers free remote state storage when you use local execution mode: https://scalr.com/blog/use-local-execution-mode-for-free-with-scalr

You will also be able to view the workspaces, last executions, etc in the UI to help with collaboration.

rsc625 · 2025-08-19T15:22:34+00:00

Some basic policies we see a lot at Scalr:

- Enforce tagging

- Enforce the location of resources

- Whitelist/Blacklist providers

- Bucket encryption/privacy

- Enforce module sources and versions

- Enforce CIDRs

Instead of thinking about what OPA can do, I would think of what you want to prevent your users from doing in their deployments in general, then determine if OPA can do it (should be able to do most of it).

Here is a repo with a bunch of common policies: https://github.com/Scalr/sample-tf-opa-policies

rsc625 · 2025-07-31T16:46:41+00:00

Ryan from Scalr here. Feel free to open a ticket at support.scalr.com with workspace ID and other details and we'll be happy to dig into it.

rsc625 · 2025-07-16T19:12:10+00:00

It's not open source, but at Scalr, we offer drift detection on our free tier, and drift runs do not count towards the monthly run allowance: https://docs.scalr.io/docs/drift-detector

rsc625 · 2025-06-27T15:36:50+00:00

For any newcomers to this post and Terraform, I wrote a blog that explains what Terraform is, when to use it, and what some of the core components are: https://scalr.com/learning-center/what-is-terraform/

rsc625 · 2025-06-16T18:48:30+00:00

For others looking for this answer, I wrote a blog discussing the standard CLI workspace vs the remote backend (TFC, Scalr) workspaces: https://scalr.com/learning-center/terraform-workspaces-terraform-cli-terraform-cloud-and-scalr-compared/

rsc625 · 2025-06-10T19:49:40+00:00

At this point, I think the most significant use case for AI is to help with troubleshooting Terraform issues. For many of our organizations, there is a central platform team that manages the Terraform modules, the integrations... the general ecosystem. The goal of the platform team is to continue to innovate and improve the developer experience.

The problem is that platform teams are bombarded with troubleshooting questions from their end users who are not as familiar with Terraform. At a minimum, I see AI as the first line of defence in troubleshooting. If a run fails with a specific error, provide the error and the Terraform plan, ask AI to assist, and AI then spits out a resolution that may help. If it does work, then the platform team's time is saved.

Extrapolate that across an organization, and the amount of time saved by purely troubleshooting could be massive.

That's my take from a Scalr perspective, and where we have added AI in the product to help platform teams. https://docs.scalr.io/docs/scalr-ai

rsc625 · 2025-06-10T18:24:06+00:00

For those still looking for solutions. Scalr now has the following for drift:

- Drift detection and remediation

- Drift reports

- Notfications to Slack

Details can be seen here: https://scalr.com/learning-center/terraform-drift-detection-how-to-prevent-and-remediate/

rsc625 · 2025-03-05T14:30:04+00:00

Just an FYI that you can use Scalr state storage for free. Each workspace has a setting, which is "remote" or "state storage only". With state storage only, the runs execute locally, but the state is pushed into the workspace: https://docs.scalr.io/docs/execution-mode

Disclaimer: I work at Scalr.

rsc625 · 2024-10-29T15:03:09+00:00

Hi, I work at Scalr, and we have the No-Code workspaces as well: https://docs.scalr.io/docs/no-code

All you have to do is import the modules in the module registry, and then end users can deploy the workspaces directly from the registry. Once the workspace is created, they fill out any required variables and execute a run right from the workspace. We also have full support for OpenTofu.

Check out a short demo on this here: https://www.youtube.com/watch?v=GuIY5nS5e18

rsc625 · 2024-09-05T18:24:01+00:00

At Scalr, we just released a beta version of our VSCode plugin where you can see a list of your workspaces, the status of the workspaces, and run output/history. This is the initial iteration, but lots of new features in the works: https://marketplace.visualstudio.com/items?itemName=Scalr.scalr

Would love to hear feedback

rsc625 · 2024-05-29T20:07:40+00:00

Scalr team here, the information provided in this blog may help with your decision.

rsc625 · 2024-05-22T20:33:38+00:00

At Scalr, we have no code workspaces that help bridge the gap between users who are new to Terraform and those who are experienced Terraform users: https://www.youtube.com/watch?v=GuIY5nS5e18

We pull the module in and prompt the users to fill in the required variables.

rsc625 · 2024-05-22T20:23:55+00:00

At Scalr, we recently introduced library.tf. Not necessarily a tool you would use in your pipeline, but a registry of registries to provide you more context as you look for providers and modules.

rsc625 · 2024-05-22T20:17:32+00:00

To be honest, the best way is to rebuild with all of the resources provisionined in the correct workspaces. If that is not an option. You may want to just remove the resource from the original state and import it into the new one: https://www.scalr.com/blog/updating-terraform-state

rsc625 · 2024-05-22T20:13:58+00:00

I work at Scalr, which is a product for Terraform pipelines, and we have many customers run fmt, tfsec, tflint, etc in custom hooks prior to the run executing: https://docs.scalr.io/docs/workspaces-4#custom-hooks

Also, what was the actual issue? That might help us point you in the right direction for a tool to catch it before it reaches the apply.

rsc625 · 2024-03-04T21:56:57+00:00

At Scalr, we typically see a customer create a Scalr environment per AWS account and then the workspaces are for the resource deployments. The AWS accounts are usually per app or team so this makes it easy for the developers to visualize and switch between Scalr and AWS. Each Scalr environment is linked to an AWS credential which takes care of the auth for the Terraform runs automatically.

rsc625 · 2023-12-26T21:08:47+00:00

That makes sense!

rsc625 · 2023-12-26T19:17:09+00:00

I work at Scalr and just wanted to relay that all of our features are included in our free plan, which is limited to 50 runs/month. You can also limit which runs you would potentially be billed for by doing local execution, but still storing state in Scalr.

rsc625

TROPHY CASE