Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore last_modified timestamp deciding whether to do an update (fixes #6) #9

Conversation

brainsik
Copy link
Contributor

@brainsik brainsik commented Jun 4, 2018

The last_modified timestamp is tied to when a user did a terraform init. This means the exact same code, checked out at different times, results in a change being detected. Ignoring the timestamp fixes this.

Changes to the function will still be detected like:

  ~ module.notify_slack_alerts.aws_lambda_function.notify_slack
      source_code_hash:                 "Y8yIL83IwWZAe4hqFlfZnXIkK27kRDm1ihkbsy9vuek=" => "U4ExxA5bGa7s1wQxb3uHUZTZZ3ONTd85Ba4DMYk7DqI="

The `last_modified` timestamp is tied to when a user did a `terraform
init`. This means the exact same code, checked out at different times,
results in a change being detected. Ignoring the time_stamp fixes this.
@brainsik
Copy link
Contributor Author

brainsik commented Jun 4, 2018

This should fix #6.

@antonbabenko
Copy link
Member

There is no argument named last_modified but only attribute - https://www.terraform.io/docs/providers/aws/r/lambda_function.html.

Let's merge it if you say it is working for you.

@antonbabenko antonbabenko merged commit 8cd1901 into terraform-aws-modules:master Jun 5, 2018
@antonbabenko
Copy link
Member

v1.4.0 has been released.

@github-actions
Copy link

I'm going to lock this pull request 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 related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants