Alerts plugin breaks deployment of large stacks 4.15

[Neifn]

Issue description

Addition of serverless alerts plugin drastically increases cloudformation size blocking deployment of larger stacks. Alerts causes issues for customers who are using third party logging and monitoring providers

Context

No response

[eahefnawy]

@Neifn could you please share your config file? I'd like to try to reproduce. I just tried deploying a simple service without alarms configured, and I don't see any alarms related resources in cloudformation template.

[Neifn]

We had some leftover configuration which caused the alarm creation, still adding new plugins when your tool forces updates makes it barely usable. frameworkVersion doesn't work properly. Latest severless version is still installed and frameworkVersion is completely ignored.

Adding our stack configuration:

{
  "service": "name",
  "frameworkVersion": "4.14.4",
  "custom": {
    ...
  },
  "plugins": [
    "serverless-plugin-datadog"
  ],
  "build": {
    "esbuild": {
      "bundle": true,
      "minify": false,
      "external": [
        "aws"
      ]
    }
  },
  "provider": {
    ...
  },
  "package": {
    "individually": true
  },
  "useDotenv": true,
  "resources": {
    "Resources": {
      ...
    }
  }
}

[eahefnawy]

@Neifn could you specifically share what's in your custom block? I'd like to see if there's anything that triggers adding the alarm resources.

[Neifn]

@eahefnawy the custom block contained some unused alerts configuration, which caused the issue, but the problem remains. The automatic update just added a plugin that was previously removed. We have already halted Serverless use for new projects and are reducing reserved credits in our subscription. Having updates forced upon us in the middle of production deployment makes your product unusable for any critical system.