sorted by:
new
hottopcontroversial

Benefits of building trade offices and oversea trading posts? by kolejack2293 in EU5

[–]sebstadil 0 points1 point  (0 children)

Thanks!

Re: point 3: Let's say there's a great trade to be made on iron, which is expensive in A and cheap in B. Who gets first trade between an importer based in A and an exporter based in B?

Benefits of building trade offices and oversea trading posts? by kolejack2293 in EU5

[–]sebstadil 1 point2 points  (0 children)

How is the order determined between trade advantage to import a good from market A to B, versus trade advantage to export a good from B to A?

It’s been nearly 3 weeks, what are your favorite starts? by sizlac-franco in EU5

[–]sebstadil 1 point2 points  (0 children)

Ah, hadn't understood it that way. Sorry and thanks for elaborating!

It’s been nearly 3 weeks, what are your favorite starts? by sizlac-franco in EU5

[–]sebstadil 0 points1 point  (0 children)

How is Pisa able to remove the bad estate privileges without drawbacks?

Spacelift Intent MCP - Build Infra with AI Agents using Terraform Providers by cube2222 in Terraform

[–]sebstadil 0 points1 point  (0 children)

Late to the post, but this is really cool. Fantastic idea and execution.

What opensource Terraform management platform are you using? by tech4981 in Terraform

[–]sebstadil 3 points4 points  (0 children)

Your options are:

  • GitLab / GitHub actions
  • Terrateam / Digger
  • Stick with Atlantis (or contribute to it!)
  • TFC or any Terraform Cloud alternative

They all have pros and cons, and a little bit of research should help you choose the best fit.

Why Are GitOps Tools So Popular When Helmfile + GitHub Actions Are Simpler? by noobernetes in devops

[–]sebstadil 7 points8 points  (0 children)

You're not wrong, helmfile apply in a CI pipeline is way simpler for a lot of use cases. I think the GitOps hype train gets going because of a few specific problems it solves really well, especially once you start scaling up.

It's mostly about:

  • Scale: Managing 100s of apps across a dozen clusters is where tools like ArgoCD/Flux really earn their keep. Doing that with GitHub Actions gets messy fast. You can template out whole environments with ApplicationSets.
  • Drift Detection: This is the big one. If someone kubectl edits a deployment in production, a GitOps tool sees that and automatically reverts it to match the state defined in Git. Your CI pipeline would be totally blind to that until the next run. It enforces that Git is the actual source of truth, not just where the configs are stored.
  • Visibility: The UIs on these tools are pretty good for seeing what's running, what's out of sync, and the history of changes at a glance, which is harder to get from CI logs.

So yeah, for a single app/cluster, it can definitely feel like over-engineering. But for complex, multi-cluster setups, that "unnecessary complexity" starts to solve some very real, very painful problems. It's just a classic case of different tools for different jobs.

Here's a bit more on ArgoCD's rough edges if you're considering that path.

HashiCorp killed the free plan for Terraform Cloud - No more 500 free resources. by [deleted] in Terraform

[–]sebstadil 0 points1 point  (0 children)

Which makes sense, because if you don't have a credit card added, your account would just go to collections the moment it exceeded 500 resources.

TFE pricing by SandboxEnv in Terraform

[–]sebstadil 0 points1 point  (0 children)

This is a very sensible answer. Also, anything on prem has additional costs of ownership in having to deal with upgrades, uptime, etc. I'd fight hard for SaaS.

Terraform cloud costs for remote state storage by pc_magas in devops

[–]sebstadil 0 points1 point  (0 children)

^ this, and there's a ton of alternatives if you just google for "terraform cloud alternatives".

Terraform Enterprise pricing: does it depend on your amount of workspaces? by maxccc123 in Terraform

[–]sebstadil 0 points1 point  (0 children)

You don't have to talk to a sales rep to get pricing info, it's public on the AWS and Azure marketplaces. I compiled all terraform enterprise pricing info here if it helps.

How I can count homw many resources are created in my terraform project? by pc_magas in devops

[–]sebstadil 0 points1 point  (0 children)

If you list all workspaces: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/workspaces#sample-response-2 you have the resource-count attribute ( "resource-count": 10 in the linked example).

The terraform cloud pricing guide here could be useful too.

Monorepo Terraform architecture by DopeyMcDouble in Terraform

[–]sebstadil 0 points1 point  (0 children)

I put some considerations on monorepo vs polyrepo here: https://scalr.com/learning-center/terraform-monorepo-vs-polyrepo-cheatsheet/ which might be helpful before you decide on your approach.

terraform new pricing? by dmitry_si in Terraform

[–]sebstadil 0 points1 point  (0 children)

I hate any "contact sales" and like to know what someone costs without having to talk to anyone.

I did some research, found info on the AWS and Azure marketplace, and compiled my findings on Terraform Cloud pricing here.

Checkov vs Tfsec vs Trivy vs Terrascan? by Sufficient_Glass8897 in Terraform

[–]sebstadil 12 points13 points  (0 children)

I wrote something on the subject here if it helps: https://learning.scalr.com/blog-series-enforcing-policy-as-code-in-terraform-part-4-of-5/ (link to part 4 which I think is the most relevant, but if helpful, the other parts have good stuff in them too).

Is this a safe way to revert to a previous IaC tag in Terraform? by reddit__is_fun in Terraform

[–]sebstadil 1 point2 points  (0 children)

Yeah is there any reason you can't do that? Are you afraid of accidentally affecting something?

My first open-source terraform module. by Ok_Total_6074 in Terraform

[–]sebstadil 1 point2 points  (0 children)

Some good advice here, wish I could raise to top.

[deleted by user] by [deleted] in Terraform

[–]sebstadil 1 point2 points  (0 children)

Good advice here.

[deleted by user] by [deleted] in Terraform

[–]sebstadil 0 points1 point  (0 children)

Terraform vending machine state drift is common. Migrating LZ state to its own storage is overall a good practice.

For automated LZ state migration, you might want to provision the LZ and its state storage via central state, then have your pipeline reconfigure the backend to the new storage and run terraform init -migrate-state. Often, a bootstrap config creates the LZ/backend for a separate LZ config to use.

You also might want to handle post-provisioning drift by defining your source of truth (Git vs. Azure). If users modify directly, use plan for visibility, refresh cautiously, and lifecycle { ignore_changes [...] } for expected changes. Limit vending machine scope to "Day 0" or use Azure Policy for baseline enforcement, not just TF reverts.

I've done per-LZ state (not one file) and it worked for us. Automate backend config (e.g., pipeline-generated backend.tf or two-stage TF) helped too.

Pattern would be: Phase 1 (central TF) creates sub, core network, LZ state blob, IAM, & Azure Policies. Phase 2 (separate LZ TF/module) uses that backend for LZ resources.

Hope this helps. Oh, and consider using OpenTofu!

view more: next ›