nx-aws
nx-aws copied to clipboard
Infrastructure as Code in CLI
Why
Lower cognitive load to setup the infrastructure
What
Just run a command to setup the infrastructure. This will generate all of it, including an IAM user and will set the configuration in a secret. The configuration can then be retrieved and added to the user's environment with another command. Read the README to clarify things.
How
We have created a new app
that contains to binaries, the one to create the infrastructure with CDK and another script to retrieve the configuration and add it to the environment.
For the IaC we use CDK, mostly because this is a very AWS specific thing, which plays nicely. We bundle things up with esbuild
which simplifies then the dependency management of the final binary as all dependencies (e.g. CDK or the secrets manager SDK) are bundled.
To follow the Nx standard of only having one apps
folder, I have moved the e2e
to such folder as well.
We have also extended the commands a little bit so the CI and publishing of the packages, will work for the new app as well.
How to test
Follow the steps in the README.md
☁️ Nx Cloud Report
CI is running/has finished running commands for commit 9b89cef0aacda7c564f581ba7d74c13e0ba12fec. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.
📂 See all runs for this CI Pipeline Execution
🟥 Failed Commands |
---|
nx-cloud record -- yarn nx format:check |
✅ Successfully ran 4 targets
Sent with 💌 from NxCloud.
up