error thrown upon subsequent apply of cloudwatchlogsforwarder module

[roshbhatia]

error thrown upon subsequent apply of cloudwatchlogsforwarder module

[himsharma01]

@roshbhatia I have looked into the issue and it is similar to one of the bug we have raised for our AWS Observability Solution[https://github.com/hashicorp/terraform-provider-aws/issues/23874] .

Problem Description

Update is failing due to a bug that “aws_serverlessapplicationrepository_cloudformation_stack” resource is not able to store values of "var.auto_enable_access_logs" (as specified in our code), on each subsequent terraform apply(s) , it detects it as change and creates a new stack-set. When the AWS API is called with a new stack-set it fails abruptly which causes the whole solution to fail while upgrading.

Alternate Approach

While we are waiting for the resolution of this issue, we have documented a work around as below:
In the file: https://github.com/SumoLogic/terraform-sumologic-sumo-logic-integrations/blob/master/aws/cloudwatchlogsforwarder/cloudwatchlogsforwarder.tf

Add the following code block in the
resource "aws_serverlessapplicationrepository_cloudformation_stack" "auto_enable_logs_subscription"

lifecycle { ignore_changes = [ parameters,tags ] }

Limitation

In the lifecycle section, we are ignoring changes in the parameter group for resource “aws_serverlessapplicationrepository_cloudformation_stack”, hence any further update to this parameter group will be ignored and respective changes cannot be made to auto-enable code.

[himsharma01]

Hey @roshbhatia , I'm looking at the issue. Please allow us sometime to investigate.

[himsharma01]

@roshbhatia I'm closing this issue. Feel free to comment/re-open for any issues.
Thanks

[axelwass]

Im stil getting this issue. Would rather have a variable that enables the ignore changes.