dbx12

joined 1 year ago
[–] dbx12@programming.dev 1 points 9 months ago

I'm not sure I follow the "only functions in the main function" rule. Does that mean you only have module blocks and no resource blocks at the top level? If yes, then I don't see the benefit of that rule in context of Terraform.

Regarding the huge state, that's something I usually try to avoid, just to avoid several minutes of "refreshing state" of the full thing. Separate projects have their own folder in Terraform, each containing the relevant resources (container, task definition etc). If I need to access info of a different project, I use terraform_remote_state and access its outputs.

[–] dbx12@programming.dev 5 points 9 months ago

You're just returning their property ^^

[–] dbx12@programming.dev 1 points 9 months ago (1 children)

But then the country you are in needs to recognize the country you're a diplomat of and want those diplomats in their country. Diplomatic status is not a "I can go where I please" status. But it's that way to sovereign citizens, I guess.

[–] dbx12@programming.dev 3 points 9 months ago (3 children)

But if they are not citizen of any nation, wouldn't that make them illegal immigrants in any country?

[–] dbx12@programming.dev 1 points 10 months ago (1 children)

So the [url]() syntax is the problem. I would say that's illegal markdown.

[–] dbx12@programming.dev 1 points 10 months ago

I want to add that Gmail is a bit of a dick when it comes to SMTP.

[–] dbx12@programming.dev 2 points 10 months ago

Hmm, I see. The perfectionist in me would want to shed that processor load though ^^

[–] dbx12@programming.dev 9 points 10 months ago (5 children)

Without any judgement: why are your servers running X11? Just because you dislike SSH'ing to them?

[–] dbx12@programming.dev 2 points 10 months ago

I know that we specifically don't use the snapshot feature for a reason. I think it has to do with how snapshots are restored. But I would need to ask my colleague why exactly we're not doing it.

We do full dumps and data-only dumps in regular intervals.

[–] dbx12@programming.dev 21 points 10 months ago (1 children)

Review is done before code gets into main, but that’s inefficient for most of the non-mission critical projects out there. A better approach is to optimistically merge most changes as soon as not-rocket-science allows it, and then later review the code in situ, in the main branch.

Assuming you have a project with continuous delivery, that is an absolute foot gun. Optimistically merge the change and then realize in situ that you forgot the WHERE part of your SQL command (or analog statement of the query builder)? No fucking thanks.

[–] dbx12@programming.dev 4 points 10 months ago

Yep, it's a repost of this one.

One could even think this OP is an alt account.

[–] dbx12@programming.dev 4 points 11 months ago

And yes, word is the word.

It seems like you are one of the twelve Americans who is unaware that the bird is the word.

view more: ‹ prev next ›