| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
Rather than the configured domain, as the corresponding SSH key
shouldn't change for the AWS domain (whereas it does for the
configured domain, if the machine changes).
|
| | |
|
| | |
|
| |
|
|
|
| |
This makes it more explicit, and works around Terraform being
unpredictable when dealing with SSH agents.
|
| |
|
|
|
| |
This can then be used to easily determine if Terraform thinks there is
a VM running.
|
| |
|
|
|
| |
In the AWS backend. This means that they don't end up on a tmpfs and
using up RAM.
|
| |
|
|
| |
To make room for data snapshots.
|
| |
|
|
|
|
| |
Which is an increase in resources from the t2.medium. The 8GB of
RAM (an increase from 4GB), will come in useful when working with data
snapshots.
|
| |
|
|
|
|
|
|
|
|
| |
For the AWS backend.
Bring it in to the Terraform configuration for the backend, where
previously only the id was known. Also, alter the provisioning so that
it can handle an empty EFS file system.
This reduces the amount of manual setup required for AWS.
|
| |
|
|
|
|
| |
This gets the AWS backend to the point where you can deploy the
backend, and then a mini environment without any actions outside of
the govuk-mini-environment-admin.
|
| |
|
|
|
| |
dns and dhcp apparently need to be specified explicitly. Also change
the network name to main.
|
| |
|
|
|
|
|
|
|
| |
Separate out the backend things, like the virtual network, from the
mini environment. This makes it easier to have resources shared
between mini environments.
Also handle the deployment of this new backend related Terraform
configuration.
|
| |
|
|
| |
To terraform.
|
| |
|
|
| |
Also annotate existing models.
|
| |
|
|
| |
And various other views and routes.
|
| | |
|
| | |
|
| |
|