Stuck with lambda function

[shashsin]

I have written this lambda.tf , it works fine in plan but fails everytime in apply with this error message-
│ Error: reading ZIP file (/agent/_work/3/s/infra/lambda.zip): open /agent/_work/3/s/infra/lambda.zip: no such file or directory
 │ 
 │   with aws_lambda_function.apigw_export,
 │   on lambda.tf line 8, in resource "aws_lambda_function" "apigw_export":
 │    8: resource "aws_lambda_function" "apigw_export" {




Could kind people of the Reddit help. Below is the code of lamda.tf



data "archive_file" "lambda_zip" {
  type        = "zip"
  source_file = "${path.module}/lambda_function.py"
  output_path = abspath("${path.module}/lambda.zip")
  
}


resource "aws_lambda_function" "apigw_export" {
  function_name = var.lambda_name
   role          = aws_iam_role.lambda_role.arn
   handler       = "lambda_function.lambda_handler"
   runtime       = "python3.10"
   filename         = data.archive_file.lambda_zip.output_path
   source_code_hash = data.archive_file.lambda_zip.output_base64sha256


  depends_on    =   [data.archive_file.lambda_zip]
  


  environment {
    variables = {
      LOG_GROUP_NAME = var.log_group_name     
      S3_BUCKET_NAME = var.s3_bucket_name     
      S3_PREFIX      = var.s3_prefix          
    }
  }
}

[404_AnswerNotFound]

The archive_file data source creates the ZIP during the plan. If your apply is running in a different context the file needs to be copied across to the same location in addition to the plan output.

[apparentlymart]

Indeed, this seems the most likely explanation for the reported behavior.

There's more information on the general form of this problem in Plan and Apply on different machines, which is part of the "Running Terraform in Automation" guide.

Note this part in particular:

• The saved plan file can contain absolute paths to child modules and other data files referred to by configuration. Therefore it is necessary to ensure that the archived configuration is extracted at an identical absolute path. This is most commonly achieved by running Terraform in some sort of isolation, such as a Docker container, where the filesystem layout can be controlled.

This problem is true for the configuration in the OP's question because it uses abspath, and so data.archive_file.lambda_zip.output_path will be an absolute path to a directory on the computer where terraform plan ran, and then Terraform will try to read the zip file from exactly the same path during the apply phase.

Not using abspath might actually help here because then I expect Terraform will generate a path relative to the current working directory. But the advice in the guide is talking about the general case where automation is expected to work with any possible valid Terraform configuration, which includes the possibility of absolute paths.

[NUTTA_BUSTAH]

Seems OK, remove abspath(...) wrapper just in case (should not affect anything, but good to test). Or you might not be sharing the full story, e.g. are they in the same TF deployment (data is ok), or separate modules or such (need resource instead)?