Remove 100% increase limit in configuration validation

[tcana1]

As of October 2014 Amazon removed the "double or halve" scaling limits (see post blog), so there is no need for the 100% validation anymore.

Thanks!

[sebdah]

The limit should already be removed in Dynamic DynamoDB. Have you seen some
issue with this?

Sebastian Dahlgren

Sent from my phone
On Nov 27, 2014 4:46 PM, "T. Canabarro" notifications@github.com wrote:

As of October 2014 Amazon removed the "double or halve" scaling limits (see
post blog
https://aws.amazon.com/blogs/aws/dynamodb-update-json-and-more/), so
there is no need for the 100% validation anymore.

Thanks!

Reply to this email directly or view it on GitHub
#225.

[tcana1]

Yes, it seems the config file parser still checks against that here. I'm using the CloudFormation stack.

[sebdah]

Seems like you're right, thanks for the report.

Sebastian Dahlgren

sebastian dahlgren | sebastian.dahlgren@gmail.com | +46 760 19 42 40 |
www.sebastiandahlgren.se | skype: sebastian.dahlgren | g+ hangouts:
sebastian.dahlgren@gmail.com

On Thu, Nov 27, 2014 at 8:57 PM, T. Canabarro notifications@github.com
wrote:

Yes, it seems the config file parser still checks against that here
https://github.com/sebdah/dynamic-dynamodb/blob/master/dynamic_dynamodb/config/__init__.py.
I'm using the CloudFormation stack.

Reply to this email directly or view it on GitHub
#225 (comment)
.

[sebdah]

This has now been released in version 1.19.2.

Thanks for the report.