aws_s3_bucket_object etag returns providers bug error

[ghost]

This issue was originally opened by @vasilij-icabbi as hashicorp/terraform#22273. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Terraform Version

Terraform v0.12.5
+ provider.aws v2.21.1
+ provider.null v2.1.2

I have a null_resource that runs a bash script locally to create a zip file:

resource "null_resource" "package_lambda" {

  triggers = {
    build_number = timestamp()
  }

  provisioner "local-exec" {
    command = "bin/package-lambda"
    interpreter = ["bash"]
  }
}

Than I have aws_s3_bucket_object resource that puts created zip file onto S3:

resource "aws_s3_bucket_object" "rss" {

  depends_on = [
    null_resource.package_lambda
  ]

  bucket = aws_s3_bucket.lambda_packages_storage.bucket
  key    = format("lambdas/%s/function.zip", local.lambdas.rss.function_name)
  source = local.lambdas.rss.path_to_file

  acl = "private"

  etag = md5(filebase64(local.lambdas.rss.path_to_file))
}

When I run terraform apply I get following error:

Error: Provider produced inconsistent final plan

When expanding the plan for aws_s3_bucket_object.rss to include new
values learned so far during apply, provider "aws" produced an invalid new
value for .etag: was cty.StringVal("92026b29f59b68ccc930d007b67b1a3b"), but
now cty.StringVal("563744635d84d0506cafce7111c9ae52").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Is there a workaround to this issues? Thank you.

[frediana]

Hello I have the same issue, any possible workaround for this issue?

thx

[lambertpan]

I fixed this by using null_resource_id, example etag = null_resource.package_lambda.id

[YakDriver]

I recommend using the source_hash argument instead. See #11522.

[github-actions]

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.