at0s/dev-tools

Common tools, to support development, in a single repo, backed by Terraform

dev-tools's Issues

Bootstrap CI/CD process

Description

Commits to master should result in the deployment/update, all that jazz. Commits to a feature branch should result in running a test suit / linters / etc

DMZ network

Description

Underlying services will self-manage private components (as there is fit/requirement), here we need to figure out the buffer zone, which will protect us from the hostilities of the Internet; implement it, and document the effort.

Backend to store Terraform state

Description

Terraform is a very flexible tool, to extend that the fully managed infrastructure state is in the hands of the developer in the form of a state file. A couple of options here, really:

1. Store the file on S3 and lock it away with DynamoDB.
2. Use TerraformCloud and it will take care of all the complexities.
3. Run Consul nearby and use it to host the state.

Would be nice to supplement this with a nice doco.

Strategy for using credentials within Terraform provider

Description

For aws provider, I had to create an actual IAM user with enabled programmatic access.
To successfully run terraform plan and terraform apply, I put credentials into my ./aws/credentials in the [default] section. This is a very naive way to manage credentials. There might be better approaches with SSO and/or role-based access.

Testing framework or approach to Terraform and serivces

Description

Far and beyond a really important topic. How can we ensure Terraform and other pieces of automation deliver exactly what we want to deliver, no more, no less?

Shared runtime for applications in containers

Problem

Applications should run in a standard environment. Containers are a natural choice here, as we are able to provide a consistent environment and somewhat standard interface for running applications. With one important question - which platform to choose for container orchestration?

K8s test

Will try the managed solution from AWS (EKS).

Done when

1. Running an instance of nginx container.
2. Able to connect to it using k8s proxy (using EKS control plane)
3. Able to connect as a regular Internet user