Terragrunt does not detect changes to remote state bucket_sse_kms_key_id

[caspar-ds]

Describe the bug

Terragrunt does not check for changes to the remote_state bucket_sse_kms_key_id config value.

Steps To Reproduce

• Initialise a new S3 remote state backend using the AWS managed KMS key
• Set bucket_sse_kms_key_id to a KMS key id
• Remove .terragrunt-cache
• Init

Expected behavior

The remote state bucket should be updated to use the CMK provided in bucket_sse_kms_key_id

Versions

• Terragrunt version: 0.66.9
• Terraform version: 1.5.7
• Environment details (Ubuntu 20.04, Windows 10, etc.): OS X

Additional context

It looks like only the bucket algorithm is used when determining if an update is required:

terragrunt/remote/remote_state_s3.go

Line 701 in 8fac874

enabled, err := checkIfSSEForS3Enabled(s3Client, config, terragruntOptions)

terragrunt/remote/remote_state_s3.go

Line 1350 in 8fac874

if *rule.ApplyServerSideEncryptionByDefault.SSEAlgorithm == fetchEncryptionAlgorithm(config) {

[shaheerkhan12605]

Not sure if this would help. For me, every time I made changes in the remote repository, I use terragrunt plan --terragrunt-source-update --terragrunt-provider-cache flags to update terragrunt cache.

[yhakbar]

Fix released in v0.67.2

[yhakbar]

The fix to address this had some unforeseen consequences. We will revisit the issue in the future as part of a breaking change.

See explanation here.