Skip to content
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

BillingMode: PAY_PER_REQUEST default #696 #705

Merged
merged 1 commit into from
Dec 7, 2018
Merged

BillingMode: PAY_PER_REQUEST default #696 #705

merged 1 commit into from
Dec 7, 2018

Conversation

Jacco
Copy link
Contributor

@Jacco Jacco commented Dec 6, 2018

*Issue #696 *

Description of changes:

Made BillingMode: PAY_PER_REQUEST default for AWS::Serverless::SimpleTable
Adjusted 6 test cases (x3=18 for all regional tests)
Added the default to the documentation

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

@codecov-io
Copy link

Codecov Report

Merging #705 into develop will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #705      +/-   ##
===========================================
- Coverage    94.17%   94.16%   -0.01%     
===========================================
  Files           67       67              
  Lines         2676     2675       -1     
  Branches       477      477              
===========================================
- Hits          2520     2519       -1     
  Misses          80       80              
  Partials        76       76
Impacted Files Coverage Δ
samtranslator/model/dynamodb.py 85.71% <ø> (ø) ⬆️
samtranslator/model/sam_resources.py 95.68% <100%> (-0.02%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40445a1...a9acdf9. Read the comment docs.

Copy link
Contributor

@jlhood jlhood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Thanks so much for doing this.

@metaskills
Copy link

metaskills commented Jan 16, 2019

Was this reverted? It is not in master anymore.

metaskills added a commit to 757rb/hello-757rb-lambda that referenced this pull request Jan 16, 2019
Allow Lambda to own a DynamoDB instance and use it for storing results of API queries to PLOS. Details to support this change include:

* Added [Aws::Record](https://github.com/aws/aws-sdk-ruby-record) gem to the project.
* Change API Gateway to use `/{resource+}` to slurp all path params.
* Pass the `query` query parameter down to the `PlosSearch` object.
* New `PlosSearchTable` DynamoDB PORO with simple schema & migration class methods.
* Made `PlosSearch#search` find or create DynamoDB records.
* Lazily create DynamoDB tables in development & test envs.
* Added an `Policies` section to the template.yml with full access to the new `PlosSearchTable` arn.

Some helpful DynamoDB resources when getting started with SAM & Ruby.

* [AWS::Serverless::SimpleTable in AWS SAM](https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlesssimpletable)
* [AWS::DynamoDB::Table in CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-dynamodb-table.html)
* [Amazon DynamoDB–related content from AWS re:Invent 2018](https://aws.amazon.com/blogs/database/amazon-dynamodb-related-content-from-aws-reinvent-2018/)
* [The Aws::Record Gem](https://github.com/aws/aws-sdk-ruby-record)
* [Announcing Amazon DynamoDB On-Demand](https://aws.amazon.com/about-aws/whats-new/2018/11/announcing-amazon-dynamodb-on-demand/)
* [Future SAM Billing Mode Issue](aws/serverless-application-model#705)

Other smaller changes include:

* Added a STAGE parameter to CloudFormation template and "prod" to deploy script.
* Created a simple Myenv PORO to check current ENV stuff.
* Renamed some logical resource id names in template.yml.
@keetonian
Copy link
Contributor

This is still in the release branch for v1.10.0. I'm working on finishing and testing the Conditions feature before we release everything in that branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants