Sadly, Cloudflare's API is garbage and you can still smell the stink through the terraform. Not to mention all the stuff they don't expose, so after an attempt to terraform it you're still stuck clicking through their dashboard.
We're deep in hypotheticals here. More restrictions mean more deserving people being denied what they need, bottom line. Which is evil. Feed everyone and sort it out after.
There's plenty of bread, you just aren't willing to share.
So we should throw out the babies with the bathwater? You need to seriously find Jesus. Spiteing the many for the deeds of the few is truly evil.
There's something more unspeakably shameful about allowing the hungry, disabled, and disadvantaged to remain so because of a few bad actors.
I would rather millions "take advantage" of the system if it meant one person didn't starve to death.
How many children died/will die because you capaticulated to Fascist? The blood is on your hands too.
Kinda makes you sound posh saying it like that. 'Why yes, Auntie Marie and I are taking a constitutional directly after our visit with the dontist."
I'm far more fond of "Fail fast." The faster you fail, the faster you can get a quality product out.
This VA military family wants you to resign. You don't represent the needs of the people.
This will get you replaced at the ballot box.
Dynamo adds complexity and is just one more part that can break. Having it only rely on s3 is far more robust. It'll all be handled under the covers anyway, so the end user won't know the difference.
Don't blame Terraform, blame the AWS API. The deeper you get, the more it boggles your mind.
If I understand what you're saying, they're both going to s3 native locking and dropping DynamoDB in basically the same way.
That's what your Gitlab pipeline is for. Anyway, Terraform is a really great tool once you get to know it's idiosyncrasies. Glad you're sticking with it!
Using Terraform to orchestrate your containers is a little overkill. You could simplify it a lot by taking Terraform out of it all together. If you run into some friction down the line, you can look at it then, but I'd start simple.
Terraform as 'cloud agnostic' is a bit of a fantasy. You can't just switch out the underlying provider without significant refactoring. To develop them in parallel would essentially be doubling the workload, which is a hard sell even in good times.
Nice, glad you figured it out. It's easy to try and throw more tools at it to get it to work and end up with a mess!
I've considered this off and on for in-house services but am still vehemently opposed to using Kubernetes to manage other infrastructure. The infra it takes to get to that point is non trivial and at that point you might as well manage the rest of it in whatever you use to spin up your first cluster
What are you trying to do? You might only need one or the other.
It's issues like this that make me wonder why the industry is moving more and more toward declarative tools. They're easier to sell to tech illiterate managers but harder to work with than scriptable solutions.
I never knew this is what I felt when this happens to me... Thanks for putting to words that feeling!
🧵 You might have noticed I haven’t announced my congressional campaign on any other platforms yet and that’s because I want to make a point:
We’re prioritizing Bluesky this election – not only because it’s more ethical, but because it just makes sense. There are four main reasons why: 1/8
This is exactly what we need right now. Makes me wish I lived in Illinois so I could support her with a vote. So a donation and a share will have to do for now!
youtu.be/Z7OhclGO3CY?...
