Releases: cloudposse/terraform-aws-ecs-alb-service-task
v0.77.0
feat: add support for availability_zone_rebalancing in aws_ecs_service resource @dmitrijn (#256)
## what * Add `availability_zone_rebalancing` attribute for [aws_ecs_service](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecs_service#availability_zone_rebalancing-1) * Update minimum AWS provider version to v5.77.why
- Useful for ecs service rebalancing
references
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-service.html#cfn-ecs-service-availabilityzonerebalancing
https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.77.0
v0.76.1
fix: redeployment_trigger: replace timestamp() with plantimestamp() @mslipets (#251)
REF: https://github.com/hashicorp/terraform-provider-aws/issues/28070what
in attempt to fix apply time issues like #28070,
replace usage of function timestamp()
with plantimestamp()
why
provided function apparently works for use cases when redeploy_on_apply
&& force_new_deployment
set to true
references
fix: update Terratest assertions with AWS account @RoseSecurity (#252)
## what- Update AWS account to fix this error:
Error: Not equal:
expected: "arn:aws:ecs:us-east-2:126450723953:cluster/eg-test-ecs-alb-service-task-ezatqz"
actual : "arn:aws:ecs:us-east-2:799847381734:cluster/eg-test-ecs-alb-service-task-ezatqz"
why
- Terratests are failing due to assertions not validating with the expected account ID
references
🤖 Automatic Updates
Migrate new test account @osterman (#249)
## 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
v0.76.0
🚀 Enhancements
feat: adds support for track_latest @gberenice (#246)
## what- Adds track_latest and bumps provider version to v5.37.0 accordingly.
why
- Allow users to make the task definitions track always the latest one if track_latest is set to true.
references
- Closes #221
- See original addition of this argument to the provider here: hashicorp/terraform-provider-aws#30154
🤖 Automatic Updates
Update .github/settings.yml @osterman (#245)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.yml
from org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
Update .github/settings.yml @osterman (#244)
## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` fileswhy
- Re-apply
.github/settings.yml
from org level - Use organization level auto-release settings
references
- DEV-1242 Add protected tags with Repository Rulesets on GitHub
v0.75.0
Add ECS Service Connect TLS and timeout @awkaplan (#235)
what
- Add support for TLS with Service Connect
- Add support for Service Connect timeouts
why
- Extend the module's functionality
references
closes #214
🤖 Automatic Updates
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#233)
what
- Update workflows (
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
action
why
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#232)
what
- Update workflows (
.github/workflows/settings.yaml
)
why
- Support new readme generation workflow.
- Generate banners
Bump golang.org/x/net from 0.17.0 to 0.23.0 in /test/src @dependabot (#230)
Bumps golang.org/x/net from 0.17.0 to 0.23.0.
Commits
c48da13
http2: fix TestServerContinuationFlood flakes762b58d
http2: fix tipos in commentba87210
http2: close connections when receiving too many headersebc8168
all: fix some typos3678185
http2: make TestCanonicalHeaderCacheGrowth faster448c44f
http2: remove clientTesterc7877ac
http2: convert the remaining clientTester tests to testClientConnd8870b0
http2: use synthetic time in TestIdleConnTimeoutd73acff
http2: only set up deadline when Server.IdleTimeout is positive89f602b
http2: validate client/outgoing trailers- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#228)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.github
repository - Simplify management of workflows from centralized hub of configuration
Bump golang.org/x/net from 0.7.0 to 0.17.0 in /test/src @dependabot (#224)
Bumps golang.org/x/net from 0.7.0 to 0.17.0.
Commits
b225e7c
http2: limit maximum handler goroutines to MaxConcurrentStreams88194ad
go.mod: update golang.org/x dependencies2b60a61
quic: fix several bugs in flow control accounting73d82ef
quic: handle DATA_BLOCKED frames5d5a036
quic: handle streams moving from the data queue to the meta queue350aad2
quic: correctly extend peer's flow control window after MAX_DATA21814e7
quic: validate connection id transport parametersa600b35
quic: avoid redundant MAX_DATA updatesea63359
http2: check stream body is present on read timeoutddd8598
quic: version negotiation- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.
Add GitHub Settings @osterman (#223)
what
- Install a repository config (
.github/settings.yaml
)
why
- Programmatically manage GitHub repo settings
Update R...
v0.74.0
🚀 Enhancements
feat: Add task_definition_arn_without_revision output @adamantike (#216)
what
- Add
task_definition_arn_without_revision
output, using thearn_without_revision
attribute fromaws_ecs_task_definition
resource. - Update minimum AWS provider version to
v4.59.0
.
why
- Useful for situations where the latest task definition is always desired.
- Avoiding manual string manipulation to strip the revision from the ARN.
references
- Added to AWS provider in version
v4.59.0
: hashicorp/terraform-provider-aws#27119
v0.73.0
Make `elb_name` optional @lagerfeuer (#215)
what
Make elb_name
in ecs_load_balancer
optional, as described in the linked Terraform docs for ECS Service.
why
Currently, when creating a service without elb_name
, Terraform will fail because it expects the variable to be set. The workaround is to set it to null
.
references
v0.72.0
🚀 Enhancements
feat: support ECS service connect @gberenice (#212)
what
- This adds support for ECS Service connect, which is already supported by the provider, see service_connect_configuration block.
why
- Extend the module's functionality.
references
- There is a PR that partially covers this feature, but unfortunately, it's not active for a while, and there are requested changes to be done: #208
v0.71.0
v0.70.0
fix external task definition must exist before first run @mightyguava (#204)
what
Change external task definition to a list(string)
so that it can be flagged on without needing the task definition to already exist.
why
Fix this issue when using an external task definition
│ 49: count = local.enabled && var.task_definition == null ? 1 : 0
│
│ The "count" value depends on resource attributes that cannot be determined
│ until apply, so Terraform cannot predict how many instances will be
│ created. To work around this, use the -target argument to first apply only
│ the resources that the count depends on.
references
Similar to how this was solved for the task role arn https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/blob/main/variables.tf#L216-L226. The workaround for now is to use -target
like mentioned in #123.
Sync github @max-lobur (#199)
Sync github from the template
v0.69.0
- No changes