Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / zendesk/lambda_deployment issues and pull requests
#15 - Deploy from s3 directly
Pull Request -
State: closed - Opened by bastien almost 6 years ago
- 6 comments
#14 - Fix for concurrency setting not getting applied for lambdas
Pull Request -
State: closed - Opened by purohitatul about 6 years ago
#13 - add option to set reserved concurrency
Pull Request -
State: closed - Opened by rbayerl over 6 years ago
#12 - use aws-sdk v3
Pull Request -
State: closed - Opened by rbayerl over 6 years ago
#11 - Deploy environment vars
Pull Request -
State: closed - Opened by ben almost 7 years ago
- 8 comments
#10 - run tests atomic so coverage is enforced per file
Pull Request -
State: closed - Opened by grosser about 7 years ago
#9 - add `rake bump:patch` etc tasks for easy and consistent gem releases
Pull Request -
State: closed - Opened by grosser about 7 years ago
#8 - run rubocop once to safe time and make failures isolated
Pull Request -
State: closed - Opened by grosser about 7 years ago
#7 - fix invalid laias_name
Pull Request -
State: closed - Opened by grosser about 7 years ago
#6 - refactor into with_env for robustness
Pull Request -
State: closed - Opened by grosser about 7 years ago
#5 - ensure alias names follows allowed pattern
Pull Request -
State: closed - Opened by rbayerl about 7 years ago
#4 - lambda aliases must start with a number
Pull Request -
State: closed - Opened by rbayerl about 7 years ago
#3 - add license to gemspec
Pull Request -
State: closed - Opened by rbayerl about 7 years ago
#2 - pin aws-sdk-core to v2; minor cleanup
Pull Request -
State: closed - Opened by rbayerl about 7 years ago
#1 - switch to travis-ci.org
Pull Request -
State: closed - Opened by rbayerl about 7 years ago