Closed ArghyaChakraborty closed 1 year ago
If you update version_id
in s3_existing_package
then Terraform will see the difference and will redeploy it:
PS: Please complete the issue template and provide the complete reproducible code next time.
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.
Description
Steps:
Possible solution: Right now, we can not provide a source_code_hash string as a module input. The source code hash is automatically computed if the file is uploaded from disk. But even if the code is from S3, we can use something like this: resource "aws_lambda_function" "example" {
other arguments ...
s3_bucket = "your_bucket_name" s3_key = "your_object_key" s3_object_version = data.aws_s3_bucket_object.package.version_id source_code_hash = data.aws_s3_bucket_object.package.version_id } So, request you to allow the
source_code_hash
as an input as well.Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the
examples/*
directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by runningterraform init && terraform apply
without any further changes.If your request is for a new feature, please use the
Feature request
template.⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]:
Terraform version:
Provider version(s):
Reproduction Code [Required]
Steps to reproduce the behavior:
Expected behavior
Actual behavior
Terminal Output Screenshot(s)
Additional context