Is there a 'best practices' github repo or other project for doing the following grunt work necessary for Infrastructure As Code?
On a past project, that development team had created a bash wrapper script that did the following work. Given arguments specifying an environment (dev, test, staging, prod), a cloudformation project github release tag, an application (one of several Rails apps), and an application github release tag, the script glued together the infrastructure and application, and started instantiating that application environment. When the infrastructure finished instantiating and servers finished booting, the application was fully up and running.
To me, this seems like boiler plate scripting that ought to be done once and shared, but I have not found anything. I also know from looking at that script that there are a couple of intricate problems that have to be solved such as adjusting the cloudformation files for the desired environment (dev, test, prod), ensuring the server installs supporting packages, and passing the environment value and a pointer for the application and its release tag to the booting server so that the server pulls that app and starts it running with that environment setup. I suspect that similar scripting can be done for Azure and Google Cloud, which is why I'm not marking this as an AWS specific question.
question from:
https://stackoverflow.com/questions/65895052/infrastructure-as-code-scripting-avoid-reinventing-the-wheel-best-practices 与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
