Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

adding support for autoscaling notification configurations #2

Merged
merged 1 commit into from
Feb 21, 2013
Merged

adding support for autoscaling notification configurations #2

merged 1 commit into from
Feb 21, 2013

Conversation

turtlebender
Copy link
Contributor

This adds first class support for the AutoScalingGroup NotificationConfigurations. I'll add at least one more example in the not too distant future

@phobologic
Copy link
Member

Nice - I'm going to go ahead and merge this, but then I'm going to update the class to use the AWSProperty class as a parent so we can ditch the init boilerplate. We still need to do this on a lot of classes in this library.

Thanks for the contribution!

phobologic added a commit that referenced this pull request Feb 21, 2013
adding support for autoscaling notification configurations
@phobologic phobologic merged commit 88d4e0a into cloudtools:master Feb 21, 2013
@bobveznat
Copy link
Member

Awesome, thank you @turtlebender.

Hons pushed a commit to Hons/troposphere that referenced this pull request Dec 23, 2014
…-notification

adding support for autoscaling notification configurations
markpeek pushed a commit that referenced this pull request May 3, 2020
* Update ApiStage to accept a dict for Throttle
The docs are vague (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-apigateway-usageplan-apistage.html), but
Throttle needs to end up like this in cfn:
```
usagePlan:
  Type: 'AWS::ApiGateway::UsagePlan'
  Properties:
    ApiStages:
      - ApiId: <your API ID>
        Stage: <API Stage>
        Throttle:
          "<resource Path>":  //(for example "/{item}/GET")
            BurstLimit: 10
            RateLimit: 5
```
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants