Description
Terraform Version
v0.11.11
Terraform Configuration Files
data "aws_s3_bucket_object" "lambda_jar_hash" {
bucket = "${var.lambda_s3_bucket}"
key = "${var.lambda_s3_key}.sha256"
}
resource "aws_lambda_function" "lambda_function_s3" {
s3_bucket = "${var.lambda_s3_bucket}"
s3_key = "${var.lambda_s3_key}"
s3_object_version = "${var.lambda_s3_object_version}"
function_name = "${var.lambda_function_name}"
role = "${var.lambda_execution_role_arn}"
handler = "${var.lambda_function_handler}"
source_code_hash = "${base64encode(data.aws_s3_bucket_object.lambda_jar_hash.body)}"
runtime = "java8"
memory_size = "${var.lambda_function_memory}"
timeout = "${var.lambda_function_timeout}"
description = "${var.description}"
reserved_concurrent_executions = "${var.reserved_concurrent_executions}"
}
Debug Output
...
~ module.comp-price-import-data-reader-scheduled-lambda.aws_lambda_function.lambda_function_s3
last_modified: "2019-01-30T11:58:32.826+0000" =>
source_code_hash: "6HVMIk6vxvBy4AApmHbQis5Av2uQeSJh3XRosmKtv0U=" => "ZTg3NTRjMjI0ZWFmYzZmMDcyZTAwMDI5OTg3NmQwOGFjZTQwYmY2YjkwNzkyMjYxZGQ3NDY4YjI2MmFkYmY0NQ=="
Plan: 0 to add, 1 to change, 0 to destroy.
Crash Output
~ module.comp-price-import-data-reader-scheduled-lambda.aws_lambda_function.lambda_function_s3
last_modified: "2019-01-30T11:58:32.826+0000" =>
source_code_hash: "6HVMIk6vxvBy4AApmHbQis5Av2uQeSJh3XRosmKtv0U=" => "ZTg3NTRjMjI0ZWFmYzZmMDcyZTAwMDI5OTg3NmQwOGFjZTQwYmY2YjkwNzkyMjYxZGQ3NDY4YjI2MmFkYmY0NQ=="
Plan: 0 to add, 1 to change, 0 to destroy.
Expected Behavior
We generate an additional file in the s3 bucket along with the lambda jar file to be deployed in s3. The additional file contains a SHA256 hash of the deployed jar file. The hash value of the file is set to the source_code_hash property of the lamba function, by using the bas64 encode function.
We would expect that the hash is stored in the tfsate and reused when applying the scripts, so that the lambda jar file is not redeployed unless the hash changes.
Actual Behavior
We applied the scripts different times without changing the jar or hash file in s3. Nevertheless terraform always redeployes the jar. The output (see above) is always the same ("6HVMIk6vxvBy4AApmHbQis5Av2uQeSJh3XRosmKtv0U=" => "ZTg3NTRjMjI0ZWFmYzZmMDcyZTAwMDI5OTg3NmQwOGFjZTQwYmY2YjkwNzkyMjYxZGQ3NDY4YjI2MmFkYmY0NQ=="). It seems the the given hash is never stored in the tfstate.