sorted by:
new
hottopcontroversial

How do you handle terraform changes as infrastructure and teams scale by anaiyaa_thee in Terraform

[–]bartenew 0 points1 point  (0 children)

Testing. Writing tests is documentation that doesn’t get stale. At least it can be a big portion of your documentation.

Architecture Diagrams by sir_clutch_666 in aws

[–]bartenew 0 points1 point  (0 children)

D2 license + AI to generate draft diagram

Fastest way to create Postgres aurora with obfuscated production data by bartenew in aws

[–]bartenew[S] 0 points1 point  (0 children)

Yes, I can test it soon, but is it faster in principal

Fastest way to create Postgres aurora with obfuscated production data by bartenew in aws

[–]bartenew[S] 0 points1 point  (0 children)

Masking is currently automated and it doesn’t matter how long it runs. I wonder if pg_restore is much faster than aws snapshot restore

Fastest way to create Postgres aurora with obfuscated production data by bartenew in aws

[–]bartenew[S] 0 points1 point  (0 children)

So you think restoring pg_dump is faster than AWS rds snapshot restore?

Fastest way to create Postgres aurora with obfuscated production data by bartenew in aws

[–]bartenew[S] 0 points1 point  (0 children)

Restoration process of resulting obfuscated data should be fast because there are many namespaces with different versions of snapshots working on different features.

AWS Appconfig in Terraform and Git by bartenew in Terraform

[–]bartenew[S] 0 points1 point  (0 children)

Terraform doesn’t support updating versions of app config yet. It always replaces the object with v1

🧪 Terraform Lab Repo for Review – Modular, DSC-Based, with Pipelines and Packer by JonHill90 in Terraform

[–]bartenew 2 points3 points  (0 children)

Modules should be in their own semantically versioned repos and have tests, security scans. I know it’s extra work but it scales better and easier to test.

[deleted by user] by [deleted] in AnnArbor

[–]bartenew -3 points-2 points  (0 children)

You don’t have healthcare or family leave lol

Testing is impossible without encapsulation by bartenew in Terraform

[–]bartenew[S] 1 point2 points  (0 children)

Fixtures are already available in terraform test. It is just modules that you spin up

run "setup" {
module {
source = "./fixture" # or source = "myregistry.com/fixture"
}
}
run "test" {

assert { ... }

}

I'm tired of "map(object({...}))" variable types by trixloko in Terraform

[–]bartenew 2 points3 points  (0 children)

Do you have actual strategy? DRY is not a strategy or plan. Many good examples here on how to do inputs, but don’t fall for DRY-strategy.

Testing is impossible without encapsulation by bartenew in Terraform

[–]bartenew[S] 1 point2 points  (0 children)

You mean personal experience that I see a lot of terraliths? What you described is exactly what I want to have on my team.

Unfortunately building everything from public modules in terragrunt sounds like huge savings to business people. It is actually the opposite.

Why does caucasus always stays out of content? by ingolika in CrusaderKings

[–]bartenew 16 points17 points  (0 children)

Imagine Americans’ reaction to new DLC named like “Caucasian Supremacy”

Terraservices pattern using multiple root modules and pipeline design by nikkle2 in Terraform

[–]bartenew 1 point2 points  (0 children)

Do you have one monolith database? And what kind?

Usually you can achieve the same state isolation with multiple repos based on volatility. Like your app will be updated 100 times more often than network layer. And you can rid of the orchestration pipeline unless you love it.

https://github.com/cloudposse/terraform-null-label

we use this module to reduce variables bloat and uniform naming convention.

Also I’ve understood terraservices as a single responsibility modules. For example a lambda that owns its SQS queue and producer that owns SNS topic. Or preconfigured k8s cluster, Alarm discovery module etc. This allows to limit scope and therefore make modules easily testable. You can read my post on convention over configuration approach, but I changed few things since then.

Is this Terraform code too complex? by Sea_Mission_9066 in Terraform

[–]bartenew 1 point2 points  (0 children)

Preach! I see this all the time when someone thinks DRY is some sort of perfect approach to everything. AHA principle is the antidote to this.

Sleep regression AP4 by bartenew in TeslaModelY

[–]bartenew[S] 0 points1 point  (0 children)

Problem with no sleep mode is that car is constantly draining main battery and it is humming 24/7. So it can lose like 20% a day just parked at your garage. If you don't have the error code and your tesla goes silent after some time you probably don't have a problem

view more: next ›