3 ms·
My experience with non-AWS providers in TF is that they're less maintained and buggy - in theory this should be easy, but people seem very afraid of TF and I ca
by jimberlage 2y ago
My experience with non-AWS providers in TF is that they're less maintained and buggy - in theory this should be easy, but people seem very afraid of TF and I can picture this getting chaotic.
But you're quite right that if they're comfortable enough, they should go into S3 and get a statefile they were happy with!
- xeraa 2y agoPermissions aren't the problem. But the upstream source of all the forks is wrong if you take a repo private, all stars from folks outside your organization are gone,... So you need GitHub support to restore everything. And the details how it happened are a bit different but it was a configuration error (making things too secure ) [I work for Elastic]
- luke-stanley 2y agoThis bears out the idea that the fastest way to get the truth on the Internet is to say something wrong first.
- xeraa 2y agoWell, it was a bad change. But we wouldn't want the wrong story make it worse. It was "just" an error in our configuration.
- luke-stanley 2y agoFair enough, and what I said was wrong too, so it's turtles all the way down! I butchered Cunningham’s Law, thank you for correcting me, though the name of the law is confusing since it was McGeady who pointed out: "The best way to get the right answer on the Internet is not to ask a question, it’s to post the wrong answer.", which is what I did, and what the parent comment did, it is attributed to the great Ward Cunningham, creator of the first Wiki, who is a rightful dude. I have nerd-sniped myself on this. At least I'm less wrong now, thank you.