search

serverless-heaven / serverless-webpack

Serverless plugin to bundle your lambdas with Webpack
MIT License
1.72k stars 417 forks source link

build(deps-dev): bump serverless from 3.39.0 to 4.3.2 #1929

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps serverless from 3.39.0 to 4.3.2.

Release notes

Sourced from serverless's releases.

4.2.5

This is another Serverless Framework V.4 GA release. If you have Serverless Framework V.4 installed already, it will auto-update within 24 hours, or you can run serverless update to get the latest version immediately. If you are upgrading to V.4 from V.3 or less, see our Upgrading to Serverless Framework V.4 Documentation.

Features

  • Added esbuild-package:package hooks to lifecycle events.

Bug Fixes

  • Fixed error reporting issue with SAM/CF support.
  • Fixed package.patterns bug when used with build.esbuild.
  • Fixed bug that improperly showed Axiom progress bar.

4.2.4

Hidden costs in AWS Lambda deployments can quickly add up, particularly from logs, metrics, and traces. These expenses often catch teams by surprise, impacting budgets and operational efficiency.

That’s where Axiom comes in—a standout observability solution that combines a sleek user experience with competitive pricing and an impressive free tier offering 500GB/month of data ingestion.

‍We’re excited to introduce Axiom’s integration with the Serverless Framework. With a simple, one-line configuration in your serverless.yml file, you can easily enhance your monitoring capabilities without breaking the bank.

Cost Comparison Switching from AWS CloudWatch to Axiom can lead to substantial cost savings due to the significant price difference between the two services:

  • Axiom: $0.15/GB of ingested data
  • AWS CloudWatch: $0.50/GB of ingested data

For example, when managing 5 TB of daily log data, Axiom’s pricing results in a total daily cost of $750 and a monthly cost of $22,500. In contrast, AWS CloudWatch costs $2,650 daily and $79,500 monthly for the same amount of data. This means that by choosing Axiom, companies can save $57,000 per month, which equates to a 70% reduction in costs compared to using CloudWatch.

These savings not only free up budget for other initiatives but also come with the added benefit of Axiom’s more powerful and user-friendly platform for managing and analyzing logs, offering deeper insights and faster problem resolution.

Set Up Axiom with the Serverless Framework Create an Axiom account (Axiom offers a very generous free tier).

Create or join an organization in Axiom–but skip the step to create a Dataset in the Axiom onboarding process, as it will be done automatically and designed per best practices by the Serverless Framework. Instead, click the setting icon in the Dashboard, select API Tokens on the left, and select New API Token.

Enter a name, choose “None” for Expiration, then click the Advanced tab to select the permissions your token should have.

Assign the Ingest, Query, Dashboards, Datasets, and Monitors permissions.

Set the AXIOM_TOKEN environment variable in your CI/CD pipeline or locally. The value should be the API token you created in Axiom.

export AXIOM_TOKEN=your-axiom-access-token

In your serverless.yml file, add the observability property to the stages block, and use axiom as the provider. Here is the easiest way to configure Axiom across all Stages within your serverless application.

service: my-api

stages:

</tr></table>

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 months ago

Superseded by #1933.