We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
CloudFormation should automatically roll back when the 5xx alarms fire.
The text was updated successfully, but these errors were encountered:
Documentation here https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_RollbackConfiguration.html
We'll need to add this as a top-level entry to serverless.yaml and add the correct Alarm resources
serverless.yaml
RollbackConfiguration: MonitoringTimeInMinutes: 30 RollbackTriggers: - Arn: !GetAtt MyAlarm.Arn Type: AWS::CloudWatch::Alarm - Arn: !GetAtt MySecondAlarm.Arn Type: AWS::CloudWatch::Alarm
Sorry, something went wrong.
We have some basic alarms defined using a Serverless Framework Plugin https://github.com/wizeline/serverless-fullstack/blob/master/serverless.yaml#L118. You'll need to look at the generated CloudFormation template to discover the correct names of the AWS::CloudWatch::Alarm Resources
denisse-dev
No branches or pull requests
CloudFormation should automatically roll back when the 5xx alarms fire.
The text was updated successfully, but these errors were encountered: