profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jamesls/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

jamesls/fakeredis 629

Fake implementation of redis API (redis-py) for testing purposes

jamesls/flask-shelve 11

Flask extension that integrates the shelve module with flask

jamesls/aws-creds-test 6

Credential testing script

jamesls/jmeslog 6

A tool for managing CHANGELOG entries

jamesls/boto 3

Python interface to Amazon Web Services

jamesls/caf 2

Generate and verify random files

jamesls/chalice 2

Python Serverless Microframework for AWS

jamesls/chalice-youtube-search 2

A port of the Youtube-Vide-Finder to the AWS Chalice framework.

jamesls/labmanager-shell 2

A command line interface for Lab Manager using their SOAP API

jamesls/flask 1

A microframework based on Werkzeug, Jinja2 and good intentions

PR merged aws/chalice

Remove support for py27

This removes package dependencies for py27 as well as updates the setup.py to not support py27. We also no longer test on py27, and the typechecker is set to check against py3.

See https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-python-2-7-in-aws-chalice/ for more info.

+54 -77

2 comments

14 changed files

jamesls

pr closed time in 9 days

push eventaws/chalice

James Saryerwinnie

commit sha 8c2f9095a710c0de80f9995f7584ece83c540b90

Remove support for py27 This removes package dependencies for py27 as well as updates the setup.py to not support py27. We also no longer test on py27.

view details

James Saryerwinnie

commit sha f92d9588e65b240083ccc28ed1a2f13e84091b2a

Add changelog for py27 removal

view details

James Saryerwinnie

commit sha ccc384d3fc1b3940ae2d6b636ffba59d55323023

Remove py2 makefile rules

view details

James Saryerwinnie

commit sha 02a03fda63d1c2aa55b010600cc02d4190906869

Rename variables

view details

James Saryerwinnie

commit sha 91bcfa20ae423c92a94f2043a28828287281b7ee

Merge branch 'py27-removal' into master * py27-removal: Rename variables Remove py2 makefile rules Add changelog for py27 removal Remove support for py27

view details

push time in 9 days

pull request commentaws/chalice

Remove support for py27

Looks like the test is failing due to a timeout error, not related to this change: /Users/runner/work/chalice/chalice/docs/source/upgrading.rst.rst:209:broken link: https://github.com/aws/chalice/issues/348 (429 Client Error: too many requests for url: https://github.com/aws/chalice/issues/348)

jamesls

comment created time in 9 days

pull request commentaws/chalice

Remove support for py27

@stealthycoin feedback incorporated.

jamesls

comment created time in 9 days

push eventjamesls/chalice

James Saryerwinnie

commit sha ccc384d3fc1b3940ae2d6b636ffba59d55323023

Remove py2 makefile rules

view details

James Saryerwinnie

commit sha 02a03fda63d1c2aa55b010600cc02d4190906869

Rename variables

view details

push time in 9 days

push eventjamesls/chalice

James Saryerwinnie

commit sha 85d5352cf8fc8b7362c64af044d4f73f8185562e

Rename variables

view details

push time in 9 days

push eventjamesls/chalice

James Saryerwinnie

commit sha 34b22189b39e724c38255884778d0319ddaed075

Remove py2 makefile rules

view details

push time in 9 days

push eventaws/chalice

Jon Beilke

commit sha 011350ecc46f96f5683ab8c9f7b5c17ac186f808

Merge pull request #1 from aws/master Pull latest upstream changes

view details

Jon Beilke

commit sha b9be128e998b12dd2ecd361a5fbf6d4c5113be89

Merge pull request #2 from aws/master Pulling latest upstream changes

view details

github-aws-sdk-python-automation@amazon.com

commit sha c52d27b7e65b6ea4632d5fda2e12ff608a992a99

Bumping version to 1.23.0

view details

Jon Beilke

commit sha d66bc5959f6f9682d7b9a80f69b03bb434c58a00

Merge branch 'aws:master' into master

view details

Jon Beilke

commit sha e9eef38259592c7251a39241b9ff1a4eba1b7e68

update terraform required_version to support 0.15 and null provider v3

view details

daka83

commit sha e4648701578ce8ab24f06a7b3cb43b006ca4b9e6

added interface for WebsocketEvent

view details

@m1ru1

commit sha e6ac3975b2326c0e30803202a3bdb6d4843cf835

Fix missing ":" after def index() from doc's code Missing ":" from line 182 def index() return {'hello': 'world'}

view details

James Saryerwinnie

commit sha fa6c89eda1c3b4b80c534b310e33f96f7acc0514

Merge pull request #1750 from am1ru1/patch-1 Fix missing ":" after def index() from doc's code

view details

James Saryerwinnie

commit sha c75ab70fa1324d0a5577b3ad2cac4f0c67e28adf

Add additional attributes to WebsocketEvent

view details

James Saryerwinnie

commit sha a9daba94fb090ff6d9efda40cf2aaf6b8a992ea6

Add changelog entry for WebsocketEvent type

view details

James Saryerwinnie

commit sha 6d9b35eb7c4e2f6d519848421cd091929458d2e2

Add changelog entry for terraform upgrade

view details

James Saryerwinnie

commit sha 6196880ce3a976cbccf7137802c404f62a8da1f4

Merge branch 'feature-terraform-015' into master PR #1738. * feature-terraform-015: Add changelog entry for terraform upgrade update terraform required_version to support 0.15 and null provider v3

view details

James Saryerwinnie

commit sha bd6e2a29f1bc23e56c8cd35612e2567764e5085e

Merge branch 'add-interface-for-websocket-event' into master PR #1749 * add-interface-for-websocket-event: Add changelog entry for WebsocketEvent type Add additional attributes to WebsocketEvent added interface for WebsocketEvent

view details

James Saryerwinnie

commit sha 98356d090ae6301218b816eadefb9b1f1e8a305a

Fix incomplete docs on packaging the vendor dir Fixes #1739.

view details

James Saryerwinnie

commit sha ad2eb55437403e41f7af6fd728058ce1cfafd9d3

Merge branch 'vendor-docs-2' into master PR #1756. * vendor-docs-2: Fix incomplete docs on packaging the vendor dir

view details

Jon Beilke

commit sha 6dc9657acc1b5bb38d18c58ecf35aa2e4f8d1a0b

update terraform required_version to support 1.0

view details

James Saryerwinnie

commit sha ee5329c126b274928a68194b2935ae4a9f363f80

Add chagnelog entry for terraform

view details

James Saryerwinnie

commit sha 6a7cdf7b1e089ba72807620d2a34940665862285

Merge branch 'feature-terraform-100' into master PR #1758. * feature-terraform-100: Add chagnelog entry for terraform update terraform required_version to support 1.0

view details

Jon Beilke

commit sha f7d6fa9c3a7a7744ad3d3845de9d9e3e734dbc04

Add source_account to aws_lambda_permission for s3 events

view details

Jon Beilke

commit sha 3b718e5272bfe4677aad7c0dd22dfd0e54741d4c

Update planner to include source account for S3 events

view details

push time in 9 days

PR merged aws/chalice

add source_account to aws_lambda_permission for lambdas with s3 events

Issue: Resolves #1635

Description of changes: Add source_account restriction for Lambda permissions with S3 events to meet AWS Foundational Security best practice: [Lambda.1] Lambda function policies should prohibit public access https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-standards-fsbp-controls.html#fsbp-lambda-1

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

+101 -33

5 comments

8 changed files

jrbeilke

pr closed time in 10 days

issue closedaws/chalice

Generated resource-based policy when deploying an on_s3_event is not secure

When deploying an app with a on_s3_event Chalice automatically generates a policy that gives invoke permissions to the specified bucket. However the bucket names is not tied to the account, so if the bucket is deleted it potentially exposes the lambda function to confused deputy attacks. An "AWS:SourceAccount" condition should be added to restrict permissions.

closed time in 10 days

szamarin

push eventaws/chalice

Jon Beilke

commit sha f7d6fa9c3a7a7744ad3d3845de9d9e3e734dbc04

Add source_account to aws_lambda_permission for s3 events

view details

Jon Beilke

commit sha 3b718e5272bfe4677aad7c0dd22dfd0e54741d4c

Update planner to include source account for S3 events

view details

James Saryerwinnie

commit sha e45bf1169ed5ffd488f5b1c13a8f0890f8077a65

Add changelog entry for source account

view details

James Saryerwinnie

commit sha 273d98c13c10105a2babbb6b5ca32e778c271a5d

Fix unresolved references in the planner

view details

James Saryerwinnie

commit sha e99fe9aa272cf2812c017af57972c04c10c02882

Merge branch 'feature-s3-event-add-account-to-lambda-policy' into master PR #1763. * feature-s3-event-add-account-to-lambda-policy: Fix unresolved references in the planner Add changelog entry for source account Update planner to include source account for S3 events Add source_account to aws_lambda_permission for s3 events

view details

push time in 10 days

push eventjamesls/chalice

James Saryerwinnie

commit sha f92d9588e65b240083ccc28ed1a2f13e84091b2a

Add changelog for py27 removal

view details

push time in 10 days

push eventjamesls/chalice

James Saryerwinnie

commit sha c68ebb62427a8991bb676f7d927fe040bc709a3c

Add changelog for py27 removal

view details

push time in 10 days

push eventjrbeilke/chalice

James Saryerwinnie

commit sha 273d98c13c10105a2babbb6b5ca32e778c271a5d

Fix unresolved references in the planner

view details

push time in 10 days

PR opened aws/chalice

Remove support for py27

This removes package dependencies for py27 as well as updates the setup.py to not support py27. We also no longer test on py27, and the typechecker is set to check against py3.

See https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-python-2-7-in-aws-chalice/ for more info.

+46 -72

0 comment

13 changed files

pr created time in 10 days

push eventjamesls/chalice

James Saryerwinnie

commit sha 8c2f9095a710c0de80f9995f7584ece83c540b90

Remove support for py27 This removes package dependencies for py27 as well as updates the setup.py to not support py27. We also no longer test on py27.

view details

push time in 10 days

pull request commentaws/chalice

add source_account to aws_lambda_permission for lambdas with s3 events

I think I have everything fixed, once we get a clean run through the tests I'll go ahead and merge.

jrbeilke

comment created time in 10 days

push eventjrbeilke/chalice

Jon Beilke

commit sha f7d6fa9c3a7a7744ad3d3845de9d9e3e734dbc04

Add source_account to aws_lambda_permission for s3 events

view details

Jon Beilke

commit sha 3b718e5272bfe4677aad7c0dd22dfd0e54741d4c

Update planner to include source account for S3 events

view details

James Saryerwinnie

commit sha e45bf1169ed5ffd488f5b1c13a8f0890f8077a65

Add changelog entry for source account

view details

James Saryerwinnie

commit sha 246cfb8252d69635278f56a7d6ae5b53701802e2

Fix unresolved references in the planner

view details

push time in 10 days

pull request commentaws/chalice

add source_account to aws_lambda_permission for lambdas with s3 events

I'm seeing an error when I try out the chalice deploy code path:


Traceback (most recent call last):
  File chalice/chalice/cli/__init__.py, line 636, in main
    return cli(obj={})
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/core.py, line 829, in __call__
    return self.main(*args, **kwargs)
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/core.py, line 782, in main
    rv = self.invoke(ctx)
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/core.py, line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/core.py, line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/core.py, line 610, in invoke
    return callback(*args, **kwargs)
  File .virtualenvs/chalice-36/lib/python3.6/site-packages/click/decorators.py, line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File chalice/chalice/cli/__init__.py, line 189, in deploy
    deployed_values = d.deploy(config, chalice_stage_name=stage)
  File chalice/chalice/deploy/deployer.py, line 376, in deploy
    return self._deploy(config, chalice_stage_name)
  File chalice/chalice/deploy/deployer.py, line 392, in _deploy
    self._executor.execute(plan)
  File chalice/chalice/deploy/executor.py, line 43, in execute
    self._default_handler)(instruction)
  File chalice/chalice/deploy/executor.py, line 53, in _do_apicall
    final_kwargs = self._resolve_variables(instruction)
  File chalice/chalice/deploy/executor.py, line 164, in _resolve_variables
    api_call.params, self.variables)
  File chalice/chalice/deploy/executor.py, line 178, in resolve_variables
    return handler(value, variables)
  File chalice/chalice/deploy/executor.py, line 206, in _resolve_dict
    final[k] = self.resolve_variables(v, variables)
  File chalice/chalice/deploy/executor.py, line 178, in resolve_variables
    return handler(value, variables)
  File chalice/chalice/deploy/executor.py, line 184, in _resolve_variable
    return variables[value.name]
KeyError: 'account_id'

I'll see if I can figure out what's going on.

jrbeilke

comment created time in 10 days

create barnchjamesls/chalice

branch : py27-removal

created branch time in 10 days

pull request commentaws/chalice

add source_account to aws_lambda_permission for lambdas with s3 events

Thanks, I'll take a look and see what's going on with the 3.6 build.

jrbeilke

comment created time in 12 days

pull request commentaws/chalice

add source_account to aws_lambda_permission for lambdas with s3 events

The change itself looks good, but before merging I'd like to also get the planner.py updated as well, so there's parity between chalice package and chalice deploy.

jrbeilke

comment created time in 17 days

PR merged aws/chalice

update terraform required_version to support 1.0

Issue: Resolves #1757

Description of changes: Bumps Terraform required_version to allow 1.0 since there are no major/breaking changes between 0.15 and 1.0 and nothing that should conflict with Chalice.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

+1 -1

1 comment

1 changed file

jrbeilke

pr closed time in 17 days

issue closedaws/chalice

Add support for terraform 1.0

And just like that Terraform 1.0 is now available: https://www.hashicorp.com/blog/announcing-hashicorp-terraform-1-0-general-availability

Unfortunately Chalice is currently limited to Terraform > 0.11.0, < 0.16.0

AFAIK there shouldn't be any breaking changes for Chalice in 1.0 since it's a continuation of 0.15, but here's the upgrade guide just in case: https://www.terraform.io/upgrade-guides/1-0.html

closed time in 17 days

jrbeilke

push eventaws/chalice

Jon Beilke

commit sha 6dc9657acc1b5bb38d18c58ecf35aa2e4f8d1a0b

update terraform required_version to support 1.0

view details

James Saryerwinnie

commit sha ee5329c126b274928a68194b2935ae4a9f363f80

Add chagnelog entry for terraform

view details

James Saryerwinnie

commit sha 6a7cdf7b1e089ba72807620d2a34940665862285

Merge branch 'feature-terraform-100' into master PR #1758. * feature-terraform-100: Add chagnelog entry for terraform update terraform required_version to support 1.0

view details

push time in 17 days

PullRequestReviewEvent

issue commentaws/chalice

How to upgrade Linux dependencies?

There's not a lot of options for upgrading packages in your Lambda runtime aside from using a custom runtime (which Chalice doesn't support). Otherwise depending on what library you're using that needs TLS 1.3 support maybe using something like pyopenssl could be an option.

serivas

comment created time in a month

PR merged aws/chalice

Fix incomplete docs on packaging the vendor dir

Fixes #1739.

+5 -1

0 comment

1 changed file

jamesls

pr closed time in a month

push eventaws/chalice

James Saryerwinnie

commit sha 98356d090ae6301218b816eadefb9b1f1e8a305a

Fix incomplete docs on packaging the vendor dir Fixes #1739.

view details

James Saryerwinnie

commit sha ad2eb55437403e41f7af6fd728058ce1cfafd9d3

Merge branch 'vendor-docs-2' into master PR #1756. * vendor-docs-2: Fix incomplete docs on packaging the vendor dir

view details

push time in a month

issue closedaws/chalice

Incomplete docs for `vendor/` directory

The following information from this doc seems incomplete:

vendor/ - The contents of this directory are automatically added to the your deployment package and its location will depend

closed time in a month

aalvrz