Use DependsOn to prevent API rate limits

[sbstjn]

• Use DependsOn to prevent failures due to API limitations (Should fix CloudFormation rate limit #3)
• Breaking: Change configuration API and replace name with table
• Breaking: Change configuration API to require CloudFormation resource instead of plain table name

Configuration

custom:
  capacities:
    - table: CustomTableA
      read:
        minimum: 1
        maximum: 123
        usage: 0.80
      write:
        minimum: 10
        maximum: 100
        usage: 0.50

CloudFormation

resources:
  Resources:
    CustomTableA:
      Type: AWS::DynamoDB::Table
      Properties:
        TableName: custom-table-A
        AttributeDefinitions:
          - AttributeName: key
            AttributeType: S
        KeySchema:
          - AttributeName: key
            KeyType: HASH
        ProvisionedThroughput:
          ReadCapacityUnits: 5
          WriteCapacityUnits: 5

[medikoo]

@sbstjn this comes as a solution for API rate limits issue. Still in documentation at "API Throtteling" section you still say:

If you plan to configure Auto Scaling for multiple DynamoDB tables or Global Secondary Indexes, request an increase of the rate limits first!

Does it mean that merged patch doesn't fix completely given issue (?) Or documentation message and this patch talk about different limits?

[sbstjn]

The default limit for PutMetricAlarm is 3 transactions per second. Depending on your tables and autoscaling configuration you still may run into this limit.

After I asked the AWS support to increase the limit (which they did without any concern) I never ran into the mentioned error again.

[medikoo]

@sbstjn thanks for reply. Was PutMetricAlarm limit issue, source of a #3 bug report that this PR tries to address (at least partially), or was it something else and PutMetricAlarm is a different thing?