You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: terraform/app/modules/ecs_service/variables.tf
+9-8Lines changed: 9 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,17 @@ variable "environment" {
6
6
7
7
variable"server_type" {
8
8
type=string
9
-
description="Type of server to be deployed. This is set as an environment variable in the main container, and is used to determine how the application is launched"
9
+
description="Type of server to be deployed. This is set as an environment variable in the main container, and is used to determine how the application is launched."
10
10
nullable=false
11
11
}
12
12
13
+
variable"server_type_name" {
14
+
type=string
15
+
description="Name of the server type to be deployed."
16
+
default=null
17
+
nullable=true
18
+
}
19
+
13
20
variable"minimum_replica_count" {
14
21
type=number
15
22
description="Minimum amount of allowed replicas for the service. Also the replica count when creating th service."
This module can be used to verify data migration tasks on a copy of actual production data before running them on production.
6
+
7
+
It creates
8
+
9
+
- A replication of a given database based on a provided snapshot
10
+
- A dedicated ECS service connected to the database
11
+
12
+
## Setup
13
+
14
+
This module is managed via a GitHub Actions workflow. To separate it from the rest of the infrastructure, the workflow uses a dedicated IAM role. To set up everything from scratch, manually create the role
15
+
`GithubDeployDataReplicationInfrastructure` based on the policy template `github_data_replication_actions_policy.json` and the trust policy `github_role_<ENVIRONMENT>_trust_policy.json`.
16
+
17
+
## Usage
18
+
19
+
### Manage the database replication infrastructure
20
+
21
+
To create the infrastructure, run the `data-replication-pipeline.yml` workflow and select the 'Recreate' option.
22
+
This will destroy any existing replication infrastructure and create a new replicated database from the latest snapshot.
23
+
24
+
To destroy the resources, run the `data-replication-pipeline.yml` with the 'Destroy' option.
0 commit comments