Skip to content

Instantly share code, notes, and snippets.

@grimm26
Created March 5, 2018 20:47
Show Gist options
  • Save grimm26/db40de2d562f46dd05c49690f79b6a14 to your computer and use it in GitHub Desktop.
Save grimm26/db40de2d562f46dd05c49690f79b6a14 to your computer and use it in GitHub Desktop.
aws_lambda_function last_modified error
> $ terraform apply
data.archive_file.funk_zip: Refreshing state...
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
+ aws_lambda_function.funk
id: <computed>
arn: <computed>
description: "Bring da funk"
filename: "/tmp/tf/funk.zip"
function_name: "funk"
handler: "funk.lambda_handler"
invoke_arn: <computed>
last_modified: <computed>
memory_size: "128"
publish: "false"
qualified_arn: <computed>
role: "arn:aws:iam::643927032162:role/iam_for_lambda"
runtime: "python3.6"
source_code_hash: "yKhWpr8W4xIA7rJ3EENJzxYvhJgE9xEJxpJvNc8dMPA="
timeout: "300"
tracing_config.#: <computed>
version: <computed>
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
aws_lambda_function.funk: Creating...
arn: "" => "<computed>"
description: "" => "Bring da funk"
filename: "" => "/tmp/tf/funk.zip"
function_name: "" => "funk"
handler: "" => "funk.lambda_handler"
invoke_arn: "" => "<computed>"
last_modified: "" => "<computed>"
memory_size: "" => "128"
publish: "" => "false"
qualified_arn: "" => "<computed>"
role: "" => "arn:aws:iam::643927032162:role/iam_for_lambda"
runtime: "" => "python3.6"
source_code_hash: "" => "yKhWpr8W4xIA7rJ3EENJzxYvhJgE9xEJxpJvNc8dMPA="
timeout: "" => "300"
tracing_config.#: "" => "<computed>"
version: "" => "<computed>"
aws_lambda_function.funk: Creation complete after 1s (ID: funk)
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
mkeisler@CLM-MKEISLER /tmp/tf [14:41:17]
> $ cd ..
mkeisler@CLM-MKEISLER /tmp [14:41:59]
> $ mv tf another
mkeisler@CLM-MKEISLER /tmp [14:42:06]
> $ cd another
mkeisler@CLM-MKEISLER /tmp/another [14:42:07] [14:42:11]
> $ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
data.archive_file.funk_zip: Refreshing state...
aws_lambda_function.funk: Refreshing state... (ID: funk)
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ aws_lambda_function.funk
last_modified: "2018-03-05T20:41:17.458+0000" => <computed>
Plan: 0 to add, 1 to change, 0 to destroy.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
mkeisler@CLM-MKEISLER /tmp/another [14:42:17]
> $ terraform apply
data.archive_file.funk_zip: Refreshing state...
aws_lambda_function.funk: Refreshing state... (ID: funk)
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ aws_lambda_function.funk
last_modified: "2018-03-05T20:41:17.458+0000" => <computed>
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
aws_lambda_function.funk: Modifying... (ID: funk)
last_modified: "2018-03-05T20:41:17.458+0000" => "<computed>"
aws_lambda_function.funk: Modifications complete after 0s (ID: funk)
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
mkeisler@CLM-MKEISLER /tmp/another [14:42:34]
> $ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
data.archive_file.funk_zip: Refreshing state...
aws_lambda_function.funk: Refreshing state... (ID: funk)
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
~ aws_lambda_function.funk
last_modified: "2018-03-05T20:41:17.458+0000" => <computed>
Plan: 0 to add, 1 to change, 0 to destroy.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment