Re:Do-nothing scripting: the key to gradual automation (2019)
by theshrike79 on Wednesday November 03, 2021 @03:42AM
(#29092038)
The possibility to ssh in an emergency is also a possibility ssh in when it's not an emergency and "just quickly change this one thing".
And then the server gets deployed via the script and the quick change isn't there any more.
Whoops.
My EC2 instances are all configured so that they can't be accessed from the outside. They boot up, fetch their install script from a set location and run it.
If they need changes, I either update the base image or the install script.
Re:Do-nothing scripting: the key to gradual automation (2019)
by csdvrx on Wednesday November 03, 2021 @04:10AM
(#29092170)
> If they need changes, I either update the base image or the install script.
You lose some time and flexibility, just because you are afraid you may forget to integrate the quick change in your scripts.
My bash histories go into a global database to avoid this
Re:Do-nothing scripting: the key to gradual automation (2019)
by nl on Wednesday November 03, 2021 @05:07AM
(#29092430)
Cattle, not pets.
Using SSH is what you do if it's a pet.
Re:Do-nothing scripting: the key to gradual automation (2019)
by ynx on Wednesday November 03, 2021 @05:55AM
(#29092664)
Well...if I'm only tending to, say, three or four cows, then they may as well be pets for my purposes, even if most of my management is systematic.
You can do a lot with four servers.
I prefer it when both the server and the deploy scripts belong to me :)
"infrastructure as code" with no way or extremely limited possibilities to ssh for emergencies strikes me as foolish overengineering / painting yourself in a corner, but if you like that, why not?