Releases: cloudposse/terraform-aws-amplify-app
v1.2.0
fix: adjust default value for custom headers variable @RoseSecurity (#47)
## what- The default custom header is currently an empty string which fails the following provider validation:
"custom_headers": {
Type: schema.TypeString,
Optional: true,
Computed: true,
ValidateFunc: validation.StringLenBetween(1, 25000),
},
Which produces the following error:
│ Error: expected length of custom_headers to be in the range (1 - 25000), got
│
│ with module.amplify_app.aws_amplify_app.default[0],
│ on .terraform/e98d/modules/amplify_app/main.tf line 28, in resource "aws_amplify_app" "default":
│ 28: custom_headers = var.custom_headers
│
- This changes the default value to
null
for thecustom_headers
variable
why
Fixes the following error:
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: expected length of custom_headers to be in the range (1 - 25000), got
│
│ with module.amplify_app.aws_amplify_app.default[0],
│ on .terraform/infra/modules/amplify_app/main.tf line 28, in resource "aws_amplify_app" "default":
│ 28: custom_headers = var.custom_headers
│
╵
references
v1.1.1
feat: amplify custom headers configuration @oycyc (#46)
## whatAllow setting custom headers in Amplify
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/amplify_app#custom-headers
From Terraform docs:
why
As said in the AWS Amplify docs:
"Custom HTTP headers enable you to specify headers for every HTTP response. Response headers can be used for debugging, security, and informational purposes. You can specify headers in the Amplify console, or by downloading and editing an app's customHttp.yml file and saving it in the project's root directory."
https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html
references
🤖 Automatic Updates
Migrate new test account @osterman (#42)
## what - Update `.github/settings.yml` - Update `.github/chatops.yml` fileswhy
- Re-apply
.github/settings.yml
from org level to getterratest
environment - Migrate to new
test
account
References
- DEV-388 Automate clean up of test account in new organization
- DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
- DEV-386 Update terratest to use new testing account with GitHub OIDC
v1.1.0
fix: Basic authentication configuration at the branch level @sestrella (#15)
what
Module consumers cannot pass a custom basic_auth_credentials
per branch using the existing variables. At the branch level, there is also a typo on enable_basic_auth
.
why
The changes made in this PR allow consumers to configure different basic authentication credentials for each branch.
🤖 Automatic Updates
chore(deps): bump the go_modules group in /test/src with 5 updates @dependabot (#40)
Bumps the go_modules group in /test/src with 5 updates:
Package | From | To |
---|---|---|
github.com/hashicorp/go-getter | 1.7.1 |
1.7.5 |
golang.org/x/crypto | 0.1.0 |
0.17.0 |
golang.org/x/net | 0.8.0 |
0.10.0 |
google.golang.org/grpc | 1.51.0 |
1.56.3 |
google.golang.org/protobuf | 1.31.0 |
1.33.0 |
Updates github.com/hashicorp/go-getter
from 1.7.1 to 1.7.5
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
v1.7.5
What's Changed
- Prevent Git Config Alteration on Git Update by
@dduzgun-security
in hashicorp/go-getter#497New Contributors
@dduzgun-security
made their first contribution in hashicorp/go-getter#497Full Changelog: hashicorp/go-getter@v1.7.4...v1.7.5
v1.7.4
What's Changed
- Escape user-provided strings in
git
commands hashicorp/go-getter#483- Fixed a bug in
.netrc
handling if the file does not exist hashicorp/go-getter#433Full Changelog: hashicorp/go-getter@v1.7.3...v1.7.4
v1.7.3
What's Changed
- SEC-090: Automated trusted workflow pinning (2023-04-21) by
@hashicorp-tsccr
in hashicorp/go-getter#432- SEC-090: Automated trusted workflow pinning (2023-09-11) by
@hashicorp-tsccr
in hashicorp/go-getter#454- SEC-090: Automated trusted workflow pinning (2023-09-18) by
@hashicorp-tsccr
in hashicorp/go-getter#458- don't change GIT_SSH_COMMAND when there is no sshKeyFile by
@jbardin
in hashicorp/go-getter#459New Contributors
@hashicorp-tsccr
made their first contribution in hashicorp/go-getter#432Full Changelog: hashicorp/go-getter@v1.7.2...v1.7.3
v1.7.2
What's Changed
- Don't override
GIT_SSH_COMMAND
when not needed by@nl-brett-stime
hashicorp/go-getter#300Full Changelog: hashicorp/go-getter@v1.7.1...v1.7.2
Commits
5a63fd9
Merge pull request #497 from hashicorp/fix-git-update5b7ec5f
fetch tags on update and fix tests9906874
recreate git config during update to prevent config alteration268c11c
escape user provide string to git (#483)975961f
Merge pull request #433 from adrian-bl/netrc-fix0298a22
Merge pull request #459 from hashicorp/jbardin/setup-git-envc70d9c9
don't change GIT_SSH_COMMAND if there's no keyfile3d5770f
Merge pull request #458 from hashicorp/tsccr-auto-pinning/trusted/2023-09-180688979
Result of tsccr-helper -log-level=info -pin-all-workflows .e66f244
Merge pull request #454 from hashicorp/tsccr-auto-pinning/trusted/2023-09-11- Additional commits viewable in compare view
Updates golang.org/x/crypto
from 0.1.0 to 0.17.0
Commits
9d2ee97
ssh: implement strict KEX protocol changes4e5a261
ssh: close net.Conn on all NewServerConn errors152cdb1
x509roots/fallback: update bundlefdfe1f8
ssh: defer channel window adjustmentb8ffc16
blake2b: drop Go 1.6, Go 1.8 compatibility7e6fbd8
ssh: wrap errors from client handshakebda2f3f
argon2: avoid clobbering BP325b735
ssh/test: skip TestSSHCLIAuth on Windows1eadac5
go.mod: update golang.org/x dependenciesb2d7c26
ssh: add (*Client).DialContext method- Additional commits viewable in compare view
Updates golang.org/x/net
from 0.8.0 to 0.10.0
v1.0.1
v1.0.0
v0.3.0
Feature/add id output @Dvelezs94 (#9)
what
- Add amplify app Id as output
why
- Useful for adding notifications through SNS and other cases
Sync github @max-lobur (#7)
Rebuild github dir from the template
v0.2.1
🚀 Enhancements
Add `sub_domains` output @aknysh (#5)
what
- Add
sub_domains
output
why
- Needed to create DNS CNAME records in the custom domain DNS zone to point to the Amplify app
sub_domains = toset([
{
"branch_name" = "dev"
"dns_record" = "dev CNAME d3id0e13ftymve.cloudfront.net"
"prefix" = "dev"
"verified" = false
},
{
"branch_name" = "main"
"dns_record" = " CNAME d3id0e13ftymve.cloudfront.net"
"prefix" = ""
"verified" = false
},
])
v0.2.0
Add a variable to provide a list of IAM policy actions for the IAM service role for the Amplify app. Update custom domain configuration @aknysh (#4)
what
- Add a variable to provide a list of IAM policy actions for the IAM service role for the Amplify app
- Update custom domain configuration. Add a new variable
domain_config
why
-
Amplify apps without a backend don't need an IAM role. Amplify apps with a backend need an IAM role, but many of them don't need a full set of actions as defined in the default set for the role. Allow specifying a custom set of actions for the IAM role. For example, for Amplify apps with server-side rendering, only the following IAM permissions are required (see Amazon CloudWatch Logs for SSR apps for more info)
logs:CreateLogStream logs:CreateLogGroup logs:DescribeLogGroups logs:PutLogEvents
-
Update custom domain configuration. Add a new variable
domain_config
. A custom domain is app-wide, not branch-wide, and needs to be specified in a separate variable (not part of the app's environments)
v0.1.0
Terraform module to provision AWS Amplify apps, backend environments, branches, domain associations, and webhooks @nitrocode (#2)
what
- Initialize module
- Setup basic app
- aws_amplify_app - create single app
- aws_amplify_branch - able to create multiple
- aws_amplify_backend_environment - able to create multiple (e.g. one for default branch, one for dev branch)
- aws_amplify_webhook - able to create multiple (one per branch)
- aws_amplify_domain_association
why
- Terraform module to provision AWS Amplify apps, backend environments, branches, domain associations, and webhooks
references
- DEV-130
- Inspired by https://github.com/masterpointio/terraform-aws-amplify-app
- https://docs.aws.amazon.com/amplify/index.html
notes
test/terratest
will not succeed since Amplify needs a GitHUb Personal Access Token (PAT) to be able to work with a repository
Error: creating Amplify App (eg-ue2-test-amplify-lzcegv): BadRequestException:
There was an issue setting up your repository. Please try again later.({"message":"Bad credentials",
"documentation_url":"https://docs.github.com/rest"})
The PAT can be read from SSM or ASM in the amplify-app
component that uses this module
data "aws_ssm_parameter" "github_pat" {
name = var.github_personal_access_token_secret_path
with_decryption = true
}