archive_file puts absolute path in state, causing changes for others users

[manojlds]

Terraform Version

0.7.2

Affected Resource(s)

• archive_file

Terraform Configuration Files

resource "archive_file" "lambda" {
  type = "zip"
  source_content = "${data.template_file.lambda.rendered}"
  source_content_filename = "lambda.js"
  output_path = "${path.module}/lambda/lambda.zip"
}

Expected Behavior

It should handle path such that it is relative and can be used by others to plan without having changes in the path being saved as absolute path.

Actual Behavior

tfstate has absolute path as output_path, and if terraform plan is run in another machine, it shows a diff just because of the different path.

[manojlds]

Should I avoid path.module and just use relative paths?

[Ninir]

@manojlds I guess this would be better

[manojlds]

Using relative path solves my problem, so closing this.

[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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.