terraform-aws-lambda icon indicating copy to clipboard operation
terraform-aws-lambda copied to clipboard

Multiple Users Cause lambda.null_resource.archive[0] timestamp Differences

Open gugaiz opened this issue 2 years ago β€’ 6 comments

Description

I am experiencing the exact same issue explained here.

The solution provided was to upgrade to v1.26.0 but I am using v3.3.1, is this a regression?

gugaiz avatar Jun 29 '22 19:06 gugaiz

I'm seeing this same behavior.

  • Module Version: 3.3.1
  • Terraform Version: v1.2.3

deybhayden avatar Jul 11 '22 15:07 deybhayden

Same too.

Module Version: 3.3.1 Terrafomr Version v1.2.2

KajiMaster avatar Jul 27 '22 18:07 KajiMaster

I was able to remedy this with the solution in https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/51#issuecomment-681978205 Basically recreate_missing_package = false in the module puts a warning message in the timestamp; effectively disabling time as a measure to recreate. Doesn't prevent new packages from being build like it claims. Needs better wording as a solution for this issue related to 'timestamp'

KajiMaster avatar Jul 28 '22 07:07 KajiMaster

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

github-actions[bot] avatar Aug 28 '22 00:08 github-actions[bot]

@KajiMaster said: "Doesn't prevent new packages from being build like it claims."

I just double-checked it again and I see the same expected behavior as before. After the package has been created and recreate_missing_package = false is specified, there won't be new zip-files created inside of builds directory on sequential terraform apply runs.

I am not sure how flexible timestamp tracking can be. Currently, it is either Yes (content will be checked based on timestamp, and the package will be recreated, if missing) or No (no timestamp will be compared).

Will it help, if a user can choose to track drift using an argument like hash (see #331) instead of timestamp like now?

antonbabenko avatar Sep 01 '22 11:09 antonbabenko

This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days

github-actions[bot] avatar Oct 02 '22 00:10 github-actions[bot]

This issue was automatically closed because of stale in 10 days

github-actions[bot] avatar Oct 12 '22 00:10 github-actions[bot]

I have added recreate_missing_package = false still terraform plan shows changes. Is it work only for terraform apply command.?

savitafulmali avatar Oct 28 '22 16:10 savitafulmali

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.

github-actions[bot] avatar Nov 28 '22 02:11 github-actions[bot]