jimjkelly / lambda-deploy Goto Github PK

View Code? Open in Web Editor NEW

13.0 2.0 7.0 17 KB

Easily Deploy Code to AWS Lambda

License: MIT License

Python 100.00%

aws-lambda boto python lambda

lambda-deploy's People

Contributors

Stargazers

Watchers

Forkers

m0ngr31 djnesmith aranga-nana sintezcs 1jkunz1 unpingco intangibleintelligence

lambda-deploy's Issues

Have Default Action be Single Upload of the Current Directory

As requested in issue #1, it might make more sense that the default deploy action is to deploy the current directory as a single Lambda, and only search for multiple Lambdas if the -d option is given. Some things to consider:

We'll want to filter out .env files then, since we don't want to by default upload their credentials
Is there any value in confirming that the entry point as specified exists? Probably. That could be good in either case.

Doesn't Recognize Region

Having issues deploying, getting NoRegionError even though region is specified

2016-12-26 22:28:33:INFO:botocore.vendored.requests.packages.urllib3.connectionpool: Starting new HTTP connection (1): 169.254.169.254
Traceback (most recent call last):
  File "/usr/local/bin/lambda-deploy", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/lambda_deploy/lambda_deploy.py", line 360, in main
    name=options.name
  File "/usr/local/lib/python2.7/dist-packages/lambda_deploy/lambda_deploy.py", line 75, in __init__
    self.client = boto3.client('lambda')
  File "/usr/local/lib/python2.7/dist-packages/boto3/__init__.py", line 83, in client
    return _get_default_session().client(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/boto3/session.py", line 263, in client
    aws_session_token=aws_session_token, config=config)
  File "/usr/local/lib/python2.7/dist-packages/botocore/session.py", line 828, in create_client
    client_config=config, api_version=api_version)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 69, in create_client
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 222, in _get_client_args
    verify, credentials, scoped_config, client_config, endpoint_bridge)
  File "/usr/local/lib/python2.7/dist-packages/botocore/args.py", line 44, in get_client_args
    endpoint_url, is_secure, scoped_config)
  File "/usr/local/lib/python2.7/dist-packages/botocore/args.py", line 101, in compute_client_args
    service_name, region_name, endpoint_url, is_secure)
  File "/usr/local/lib/python2.7/dist-packages/botocore/client.py", line 295, in resolve
    service_name, region_name)
  File "/usr/local/lib/python2.7/dist-packages/botocore/regions.py", line 122, in construct_endpoint
    partition, service_name, region_name)
  File "/usr/local/lib/python2.7/dist-packages/botocore/regions.py", line 135, in _endpoint_for_partition
    raise NoRegionError()
botocore.exceptions.NoRegionError: You must specify a region.

In my .env.lambda:
AWS_DEFAULT_REGION = us-east-1

I even hard coded region into regions.py still doesn't work

Add setup.cfg to Fix Homebrew Python pip Install Bug

As is referenced here there is a way to directly solve the Homebrew pip install bug in our codebase, so do that instead of showing the link in the error message.

Issue deploying on Windows 10

Trying to get this going on Windows, but running into an error:

2016-04-18 11:38:33:INFO:botocore.credentials: Found credentials in environment variables.
2016-04-18 11:38:33:INFO:lambda_deploy: Packaging lambda .env
Traceback (most recent call last):
  File "C:\Users\Joe\appdata\local\scoop\apps\python27\2.7.10\scripts\lambda-deploy-script.py", line 9, in <module>
    load_entry_point('lambda-deploy==0.0.1', 'console_scripts', 'lambda-deploy')()
  File "C:\Users\Joe\appdata\local\scoop\apps\python27\2.7.10\lib\site-packages\lambda_deploy\lambda_deploy.py", line 321, in main
    method()
  File "C:\Users\Joe\appdata\local\scoop\apps\python27\2.7.10\lib\site-packages\lambda_deploy\lambda_deploy.py", line 133, in deploy
    zfh = self.package(lambda_name)
  File "C:\Users\Joe\appdata\local\scoop\apps\python27\2.7.10\lib\site-packages\lambda_deploy\lambda_deploy.py", line 98, in package
    if 'requirements.txt' in os.listdir(src_dir):
WindowsError: [Error 267] The directory name is invalid: 'C:\\Dev\\python\\kodi-alexa-master\\.env/*.*'

This is my .env file:

AWS_ACCESS_KEY_ID=***********
AWS_SECRET_ACCESS_KEY=*****************
LAMBDA_ROLE=lambda_basic_execution
LAMBDA_TIMEOUT=30

It looks like it's trying to use .env as a directory that everything is in. Anything I can try?

Use Constants Where Appropriate for Dictionary Construction

And related... for example

{
    'jti': jti,
}

If only we had that sweet JavaScript { jti } syntax. :)

Problem deploying kodi skill to AWS

I've followed all the steps detailed in this read me; https://github.com/m0ngr31/kodi-alexa#aws-lambda. I'm having some issues deploying to AWS - it hangs for quite some time while deploying then comes up with the following message.
Can you suggest where I am going wrong?

jimjkelly / lambda-deploy Goto Github PK

lambda-deploy's People

Contributors

Stargazers

Watchers

Forkers

lambda-deploy's Issues

Have Default Action be Single Upload of the Current Directory

Doesn't Recognize Region

Add setup.cfg to Fix Homebrew Python pip Install Bug

Issue deploying on Windows 10

Use Constants Where Appropriate for Dictionary Construction

Problem deploying kodi skill to AWS

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent