2.0.1

This release adds CDK usage examples and a sample CDK project! Contributed by @ssamueluk

2.0.0

📣 This is a major release for AWS SAM and CloudFormation support! This feature was contributed by @ssamueluk.

🐿 SAM and ☁️ CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.

• BREAKING CHANGE: The dashboard names now include a region identifier so the same service can be deployed to multiple regions in the same account.
• BREAKING CHANGE: The alarm name has changed slightly for each service. Every alarm begins with the service name followed by an underscore. This was done for two reasons:

1. To ensure some consistency in alarm names
2. SLIC Watch now supports resources that do not explcitly set a name
   (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
   we generate logical IDs for CloudFormation Alarm resources. Since we
   have changed the logical ID, CloudFormation will create new Alarms to
   replace the previous one before it deletes the old one. We had to
   ensure that the alarm name would differ from the previous name or an
   AlarmName conflict would result, failing the CloudFormation deployment

2.0.0-rc6

What's Changed

• Fixes slic-watch-core as a full dependency of the serverless plugin

This is a pre-release to allow testing of major new features.

• 🐿 SAM and ☁️ CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
• Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.
• BREAKING CHANGE: The alarm name has changed slightly for each service.
  Every alarm begins with the service name followed by an underscore.
  This was done for two reasons:
  1. To ensure some consistency in alarm names
  2. SLIC Watch now supports resources that do not explcitly set a name
     (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
     we generate logical IDs for CloudFormation Alarm resources. Since we
     have changed the logical ID, CloudFormation will create new Alarms to
     replace the previous one before it deletes the old one. We had to
     ensure that the alarm name would differ from the previous name or an
     AlarmName conflict would result, failing the CloudFormation deployment

2.0.0-rc5

What's Changed

• Fixes slic-watch-core as a full dependency of the serverless plugin

This is a pre-release to allow testing of major new features.

• 🐿 SAM and ☁️ CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
• Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.
• BREAKING CHANGE: The alarm name has changed slightly for each service.
  Every alarm begins with the service name followed by an underscore.
  This was done for two reasons:
  1. To ensure some consistency in alarm names
  2. SLIC Watch now supports resources that do not explcitly set a name
     (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
     we generate logical IDs for CloudFormation Alarm resources. Since we
     have changed the logical ID, CloudFormation will create new Alarms to
     replace the previous one before it deletes the old one. We had to
     ensure that the alarm name would differ from the previous name or an
     AlarmName conflict would result, failing the CloudFormation deployment

2.0.0-rc4

What's Changed

This is a pre-release to allow testing of major new features.

• 🐿 SAM and ☁️ CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
• Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.
• BREAKING CHANGE: The alarm name has changed slightly for each service.
  Every alarm begins with the service name followed by an underscore.
  This was done for two reasons:
  1. To ensure some consistency in alarm names
  2. SLIC Watch now supports resources that do not explcitly set a name
     (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
     we generate logical IDs for CloudFormation Alarm resources. Since we
     have changed the logical ID, CloudFormation will create new Alarms to
     replace the previous one before it deletes the old one. We had to
     ensure that the alarm name would differ from the previous name or an
     AlarmName conflict would result, failing the CloudFormation deployment

2.0.0-rc3

What's Changed

This is a pre-release to allow testing of major new features.

• 🐿 SAM and ☁️ CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
• Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.
• BREAKING CHANGE: The alarm name has changed slightly for each service.
  Every alarm begins with the service name followed by an underscore.
  This was done for two reasons:
  1. To ensure some consistency in alarm names
  2. SLIC Watch now supports resources that do not explcitly set a name
     (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
     we generate logical IDs for CloudFormation Alarm resources. Since we
     have changed the logical ID, CloudFormation will create new Alarms to
     replace the previous one before it deletes the old one. We had to
     ensure that the alarm name would differ from the previous name or an
     AlarmName conflict would result, failing the CloudFormation deployment

2.0.0-rc2

What's Changed

This is a pre-release to allow testing of major new features.

• SAM and CloudFormation support! - Support for AWS SAM and CloudFormation projects is available now with the SLIC Watch CloudFormation Macro. See the README for setup instructions and let us know your feedback
• Better support for resources with no provided name. CloudFormation resources that do not provide the optional resource name are now supported for all services.
• BREAKING CHANGE: The alarm name has changed slightly for each service.
  Every alarm begins with the service name followed by an underscore.
  This was done for two reasons:
  1. To ensure some consistency in alarm names
  2. SLIC Watch now supports resources that do not explcitly set a name
     (e.g. Lambda FunctionName or DynamoDB TableName). This changed how
     we generate logical IDs for CloudFormation Alarm resources. Since we
     have changed the logical ID, CloudFormation will create new Alarms to
     replace the previous one before it deletes the old one. We had to
     ensure that the alarm name would differ from the previous name or an
     AlarmName conflict would result, failing the CloudFormation deployment

1.3.0

What's Changed

• Add support for SNS alarms and dashboard by @direnakkocdemir in #83
• Ensure extended statistics can be used in Alarm descriptions by @eoinsha in #82

New Contributors

• @direnakkocdemir made their first contribution in #83

Full Changelog: 1.2.0...1.3.0

1.2.0

What's Changed

• Add support for ECS utilization metrics and dashboard by @eoinsha and @direnakkocdemir in #81

Full Changelog: 1.1.0...1.2.0

1.1.0

What's Changed

• Add support for The Serverless Framework v3. v2 is still supported!
• change properties to add type objects by @dchocoboo in #77
• Updates test project to sls v3 and solve datetime validation issue by @lmammino in #80

New Contributors

• @dchocoboo made their first contribution in #77

Full Changelog: 1.0.7...1.1.0