-
-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
source_path
does not support fully-specified option set
#12
Comments
Hi @tkalus ! You are right that this functionality is not there. We have been reworking & finishing it up after README was written ( Thanks for proposing help with this, but we don't need it for this issue because it is almost done, and will be released later today or tomorrow. |
v1.10.0 has been just released with rather complete support for |
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. |
source_path
only accepts a single string detailing a directory or filename. Docs detail that a list of strings or a list of maps are supported, but anything other than a string causes a failure.Expected Behavior
Ability to specify a list of maps to describe what to include in the Lambda package.
Actual Behavior
Failure during
external.archive_package
step in package.tf; similar failure seen with github-tagged version.Steps to repro
Run
terraform apply
with the following configWhere the
src
directory contains the contents of this repo's examples/fixtures/python3.8-app1 directory.Failure observed:
Changing
source_path = jsonencode(var.source_path)
fixed that error, but examination of lambda.py:248 leads me to believe the functionality simply isn't present as the external process is only ever expecting asource_path
to be a string detailing a pathname.I'd be happy to look into extending lambda.py to accept additional options, but if it's something already being worked on, I'd just as soon not spend my time on it.
The text was updated successfully, but these errors were encountered: