diff --git a/docs/discussions/knowledge-base/637.mdx b/docs/discussions/knowledge-base/637.mdx new file mode 100644 index 0000000000..e9ef263777 --- /dev/null +++ b/docs/discussions/knowledge-base/637.mdx @@ -0,0 +1,27 @@ +--- +hide_table_of_contents: true +hide_title: true +custom_edit_url: null +--- + +import CenterLayout from "/src/components/CenterLayout" +import GitHub from "/src/components/GitHub" + + + + + + +Knowledge Base +

Changes to ecs-deploy runner module not working on plan

+\n

Tracked in ticket #109799

\n\n","bodyHTML":"

Hello,

\n

I am facing two different issues in the ecs-deploy-runner module at: \"git::git@github.com:gruntwork-io/terraform-aws-service-catalog.git//modules/mgmt/ecs-deploy-runner\" using ref=v0.67.0.

\n

ISSUE 01:

\n
    \n
  1. Upgrading from v.0.67.0 tov 0.95.1
  2. \n
\n

On the plan I am receiving the following error. Is there anything I need to be doing from my end to be able to switch to the version 0.95.1.

\n

\"Screenshot

\n

ISSUE 02:
\nI am trying to change the cloudwatch log group retention in days for ecs-deploy-runner.

\n

But, when I set

\n
inputs = {\n\n  # Setting up cloudwatch log group retention (in days)\n  invoker_lambda_cloudwatch_log_group_retention_in_days = 2\n\n}\n
\n

in terragrunt.hcl for ecs-deploy runner - the plan returns with No changes. Your infrastructure matches the configuration.. But I can confirm that the cloudwatch log group's retention in the aws console is set to 3, and should therefore not return as No changes.
\nIf I make changes to other variables such as container_max_memory it would be reflected correctly on the plan.

\n
\n\n

Tracked in ticket #109799

\n
","answer":{"body":"@sewmiuraj for issue number 1, this is caused by a limitation of terraform. It requires a provider to be provisioned for each AWS region. The fix is to update `multi_region_common.hcl` to have the latest list of regions. Here is a snippet of what the current list of regions should look like:\r\n\r\n```\r\n all_aws_regions = [\r\n \"af-south-1\",\r\n \"ap-east-1\",\r\n \"ap-northeast-1\",\r\n \"ap-northeast-2\",\r\n \"ap-northeast-3\",\r\n \"ap-south-1\",\r\n \"ap-south-2\",\r\n \"ap-southeast-1\",\r\n \"ap-southeast-2\",\r\n \"ap-southeast-3\",\r\n \"ca-central-1\",\r\n \"cn-north-1\",\r\n \"cn-northwest-1\",\r\n \"eu-central-1\",\r\n \"eu-central-2\",\r\n \"eu-north-1\",\r\n \"eu-south-1\",\r\n \"eu-south-2\",\r\n \"eu-west-1\",\r\n \"eu-west-2\",\r\n \"eu-west-3\",\r\n \"me-south-1\",\r\n \"me-central-1\",\r\n \"sa-east-1\",\r\n \"us-east-1\",\r\n \"us-east-2\",\r\n \"us-gov-east-1\",\r\n \"us-gov-west-1\",\r\n \"us-west-1\",\r\n \"us-west-2\"\r\n ]\r\n```\r\n\r\nYour second issue is slightly more involved, I'll do some investigation and get back to you.","bodyHTML":"

@sewmiuraj for issue number 1, this is caused by a limitation of terraform. It requires a provider to be provisioned for each AWS region. The fix is to update multi_region_common.hcl to have the latest list of regions. Here is a snippet of what the current list of regions should look like:

\n
 all_aws_regions = [\n    \"af-south-1\",\n    \"ap-east-1\",\n    \"ap-northeast-1\",\n    \"ap-northeast-2\",\n    \"ap-northeast-3\",\n    \"ap-south-1\",\n    \"ap-south-2\",\n    \"ap-southeast-1\",\n    \"ap-southeast-2\",\n    \"ap-southeast-3\",\n    \"ca-central-1\",\n    \"cn-north-1\",\n    \"cn-northwest-1\",\n    \"eu-central-1\",\n    \"eu-central-2\",\n    \"eu-north-1\",\n    \"eu-south-1\",\n    \"eu-south-2\",\n    \"eu-west-1\",\n    \"eu-west-2\",\n    \"eu-west-3\",\n    \"me-south-1\",\n    \"me-central-1\",\n    \"sa-east-1\",\n    \"us-east-1\",\n    \"us-east-2\",\n    \"us-gov-east-1\",\n    \"us-gov-west-1\",\n    \"us-west-1\",\n    \"us-west-2\"\n  ]\n
\n

Your second issue is slightly more involved, I'll do some investigation and get back to you.

"}}} /> + +
+ + +