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
feat!: Upgrade AWS provider and min required Terraform version to 6.0 and 1.5.7 respectively (#38)
* feat: Bump MSV of Terraform and AWS provider, update attribute lookup syntax, change policies from list to map
* feat: Bump versions, add missing arguments and variable type definitions
* feat: Add support for region arguments and upgrade guide
* chore: Lower min supported Terraform version
If you find a bug, please open an issue with supporting configuration to reproduce.
9
+
10
+
## List of backwards incompatible changes
11
+
12
+
- Terraform v1.5.7 is now minimum supported version
13
+
- AWS provider v6.0.0 is now minimum supported version
14
+
-`instance_iam_role_additional_policies`, `service_iam_role_additional_policies`, `spot_fleet_iam_role_additional_policies` types are now `map(string)` instead of `list(string)`
15
+
- IAM assume role policy SIDs have been modified to match their use (previously all were `ECSAssumeRole` which is inaccurate)
16
+
-`compute_environment_order` is now a required argument for `aws_batch_job_queue` per the Batch API and replaces `compute_environments`
17
+
18
+
## Additional changes
19
+
20
+
### Added
21
+
22
+
- Support for `region` parameter to specify the AWS region for the resources created if different from the provider region.
23
+
- Support for `compute_environment_order`, `job_state_time_limit_action`, `timeouts` arguments for job queues
24
+
- All (currently) supported arguments for `eks_properties` argument have been added to the job definition resource
25
+
- Support for `scheduling_priority` and `node_properties` arguments for job definitions
26
+
27
+
### Modified
28
+
29
+
- Variable definitions now contain detailed `object` types in place of the previously used any type.
30
+
-`compute_environment_name` argument has been changed to `name` per provider `v6.x` API; no-op for users
31
+
-`compute_environment_name_prefix` argument has been changed to `name_prefix` per provider `v6.x` API; no-op for users
32
+
33
+
### Removed
34
+
35
+
- None
36
+
37
+
### Variable and output changes
38
+
39
+
1. Removed variables:
40
+
41
+
- None
42
+
43
+
2. Renamed variables:
44
+
45
+
- None
46
+
47
+
3. Added variables:
48
+
49
+
- None
50
+
51
+
4. Removed outputs:
52
+
53
+
- None
54
+
55
+
5. Renamed outputs:
56
+
57
+
- None
58
+
59
+
6. Added outputs:
60
+
61
+
- None
62
+
63
+
## Upgrade State Migrations
64
+
65
+
### Before 2.x Example
66
+
67
+
```hcl
68
+
module "batch" {
69
+
source = "terraform-aws-modules/batch/aws"
70
+
version = "2.1.0"
71
+
72
+
# Truncated for brevity, only relevant module API changes are shown ...
... # Other properties for a_ec2 compute environment
108
+
}
109
+
110
+
b_ec2_spot = {
111
+
... # Other properties for b_ec2_spot compute environment
112
+
}
113
+
}
114
+
# Now required
115
+
compute_environment_order = {
116
+
0 = {
117
+
compute_environment_key = "a_ec2"
118
+
}
119
+
1 = {
120
+
compute_environment_key = "b_ec2_spot"
121
+
}
122
+
}
123
+
124
+
tags = local.tags
125
+
}
126
+
```
127
+
128
+
To migrate from the `v2.x` version to `v3.x` version example shown above, the following state move commands can be performed to maintain the current resources without modification:
129
+
130
+
```bash
131
+
# For each additional policy in instance_iam_role_additional_policies, simply move the prior value to the new key you have defined in your configuration
132
+
# This can be done similarly for aws_iam_role_policy_attachment.service and aws_iam_role_policy_attachment.spot_fleet
0 commit comments