Closed svbernem closed 1 month ago
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
This issue was automatically closed because of stale in 10 days
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.
The problem described in issue https://github.com/terraform-aws-modules/terraform-aws-lambda/issues/339 still exists. I would have just commented below that issue, but it was closed by a bot without any resolution.
Terraform will detect changes of lambdas when the absolute paths to the zipped local lambda source changes, thus using terraform from different computers and/or CI/CD will lead to tons of noise. Are there any updates about this? In my case this noise completely dominates the terraform apply output, making it very hard to spot actual changes and thus increasing the risk of errors, security issues and so on.