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
This directory contains reusable Terraform modules that can be resused for multiple resource instances. Each module is designed to encapsulate specific functionality, making it easier to manage and deploy infrastructure components consistently.
4
+
5
+
Each module includes its own `README.md` file with detailed information on usage, inputs, outputs, and examples.
|[aws_iam_policy_document.app_config_policy](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document)| data source |
55
+
54
56
## Inputs
55
57
56
58
| Name | Description | Type | Default | Required |
| <aname="input_environment"></a> [environment](#input\_environment)| Deployment environment tag used for naming and labeling (e.g., dev, prod) |`string`| n/a | yes |
62
64
| <aname="input_owner"></a> [owner](#input\_owner)| Identifies the team or person responsible for the resource (used for tagging). |`string`| n/a | yes |
If any app configurations are modified manually e.g. new flag version, terraform will not be able to delete the App Config instances as it does not own the Feature Flag versions.
4
-
Therefore we have three instances of the configuration per deployment.
4
+
Therefore we have three instances of the configuration per deployment.
5
5
6
6
{date}-dev.json (sandboxes, dev and test)
7
7
{date}-pre-prod.json
8
8
{date}-prod.json
9
9
10
-
It is recomended that all feature flags are enabled for the dev version to reduce manual app config actions.
11
-
The prod version should be set to what we expect our prod instances to represent.
10
+
It is recomended that all feature flags are enabled for the dev version to reduce manual app config actions.
11
+
The prod version should be set to what we expect our prod instances to represent.
0 commit comments