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: CHANGELOG.md
+5
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,11 @@
2
2
3
3
## [Unreleased]
4
4
5
+
## [0.12.0] - 2022-04-07
6
+
7
+
- Ensure compatibility with AWS Provider Version 4 ([#286](https://github.com/milliHQ/terraform-aws-next-js/issues/286), [#291](https://github.com/milliHQ/terraform-aws-next-js/pull/291))
8
+
- Add switch for attaching additional policy documents ([#276](https://github.com/milliHQ/terraform-aws-next-js/pull/276))
9
+
5
10
## [0.11.5] - 2022-04-02
6
11
7
12
- Adds support for route-manifest v4 ([#292](https://github.com/milliHQ/terraform-aws-next-js/pull/292))
Copy file name to clipboardExpand all lines: README.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ terraform {
113
113
required_providers {
114
114
aws = {
115
115
source = "hashicorp/aws"
116
-
version = "~> 3.0"
116
+
version = "~> 4.0"
117
117
}
118
118
}
119
119
}
@@ -199,13 +199,13 @@ You can create a `.terraformignore` in the root of your project and add the foll
199
199
| Name | Version |
200
200
|------|---------|
201
201
| terraform | >= 0.15 |
202
-
| aws | >= 3.64.0|
202
+
| aws | >= 4.8|
203
203
204
204
## Providers
205
205
206
206
| Name | Version |
207
207
|------|---------|
208
-
| aws | >= 3.64.0|
208
+
| aws | >= 4.8|
209
209
210
210
## Inputs
211
211
@@ -227,6 +227,7 @@ You can create a `.terraformignore` in the root of your project and add the foll
227
227
| deployment\_name | Identifier for the deployment group (only lowercase alphanumeric characters and hyphens are allowed). |`string`|`"tf-next"`| no |
228
228
| expire\_static\_assets | Number of days after which static assets from previous deployments should be removed from S3. Set to -1 to disable expiration. |`number`|`30`| no |
229
229
| image\_optimization\_lambda\_memory\_size | Amount of memory in MB the worker Lambda Function for image optimization can use. Valid value between 128 MB to 10,240 MB, in 1 MB increments. |`number`|`2048`| no |
230
+
| lambda\_attach\_policy\_json | Whether to deploy additional lambda JSON policies. If false, lambda\_policy\_json will not be attached to the lambda function. (Necessary since policy strings are only known after apply when using Terraforms data.aws\_iam\_policy\_document) |`bool`|`false`| no |
230
231
| lambda\_attach\_to\_vpc | Set to true if the Lambda functions should be attached to a VPC. Use this setting if VPC resources should be accessed by the Lambda functions. When setting this to true, use vpc\_security\_group\_ids and vpc\_subnet\_ids to specify the VPC networking. Note that attaching to a VPC would introduce a delay on to cold starts |`bool`|`false`| no |
231
232
| lambda\_environment\_variables | Map that defines environment variables for the Lambda Functions in Next.js. |`map(string)`|`{}`| no |
232
233
| lambda\_memory\_size | Amount of memory in MB a Lambda Function can use at runtime. Valid value between 128 MB to 10,240 MB, in 1 MB increments. |`number`|`1024`| no |
description="Whether to deploy additional lambda JSON policies. If false, lambda_policy_json will not be attached to the lambda function. (Necessary since policy strings are only known after apply when using Terraforms data.aws_iam_policy_document)"
0 commit comments