Issue deploying on Windows 10 about lambda-deploy HOT 8 CLOSED

Hmm, definitely a bug. Two work around while I work on a fix:

One, put your lambda or lambdas in a separate directory and point the tool at that:

current_directory
  |- .env
  |- lambdas
      |- your_lambda_dir

Then in current_directory, run lambda_deploy like so:

$ lambda-deploy -d lambdas deploy

The other option, especially if you only have one to upload, is to specify the lambda:

$ lambda-deploy deploy your_lambda_dir

from lambda-deploy.

Also - I'm definitely interested to hear about your experiences on Windows - I haven't tested this there at all so I'd like to hear if it works.

from lambda-deploy.

Yeah, I tried that after I wrote the issue and it seemed to work.

Once I figured out how to use yaep to use the environment variables, this turned into a pretty great way to deploy to lambda, glad I found the project! Now I can't wait to get a version where I can have it in the same directory.

from lambda-deploy.

Should be a 0.0.2 version up now - let me know if this fixes the problem, thanks!

from lambda-deploy.

It seems to fix the issue, but it just stops what it's doing:

$ lambda-deploy deploy
2016-04-18 14:32:21:INFO:botocore.credentials: Found credentials in environment variables.

Doesn't upgrade or anything.

from lambda-deploy.

So you have a layout like:

current_directory (where you run lambda-deploy from)
  | - .env
  | - your_lambda_directory

?

Or are you trying to upload from inside "your_lambda_directory"?

from lambda-deploy.

Trying to do it inside of the lambda directory if that's possible

from lambda-deploy.

Hmm. I'll have to give some though to that, I guess I didn't really think much about uploading individual Lambdas. I have a stable of them that I keep in a repo with the idea that the tool can run on a CI machine to deploy them on commit (obviously blindly just updating them all, but no big deal).

I guess I could have the "search" logic to find lambda folders only operate if you give the -d argument to specify a directory, and otherwise assume there's a single lambda in the current directory.

That'll probably take some time though. I'll look into it.

from lambda-deploy.