terraform apply and plan is broken with carriage return in opsworks custom.json template file

[hashibot]

This issue was originally opened by @ole-flaregames as hashicorp/terraform#9351. It was migrated here as part of the provider split. The original body of the issue is below.

---

Hi there,

found a pretty strange issue. It seems like a carriage return at the bottom of a template.json are "compared / diffed / parsed" in a wrong way with the actually applied state within opsworks.
It seems only to afffect version 0.7.5

Terraform Version

0.7.5

Affected Resource(s)

• aws_opsworks_stack

Terraform Configuration Files

Attached as file

1. opsworks-create-stack.tf includes the data "template_file" + the module that is used for creating an opsworks stack

2. config_stack.json is the template file itself that is rendered

Expected Behavior

As there are no changes within the custom.json - terraform should not try to apply or suggest any changes that are related to the custom.json during plan or apply.

Actual Behavior

terraform plan suggests changes , terraform apply - really applies changes although there are none - Actually if you apply the changes for the custom.json they are the same in Opsworks as before.

Steps to Reproduce

• create a opsworks stack with a custom.json
• the template file includes a carriage return at the end of the template.json

• apply initially
• the next plan or apply will show changes , but actually there are none

What i suspect to be a cause of the problem:
It seems like the carriage return "/n" within the template is deleted by the Opsworks API.
A strong indication for this issue is, that terraform plan or terraform applyshow in their change list an additional "/n" after the whole custom.json block.

If you delete the carriage return (bottom line) within the template file, the issue seems to be fixed.

Additional information:
Usage of S3 remote state files.

Cheers
Ole

opsworks-create-stack.tf.txt
config_stack.json.txt

[repl-raymond-bolander]

We are seeing a similar issue as well.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!