Skip to content
New issue

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

fix(syncer): bump @aws-lambda-powertools/logger from 1.6.0 to 1.7.0 in /modules/runner-binaries-syncer/lambdas/runner-binaries-syncer #3111

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 27, 2023

Bumps @aws-lambda-powertools/logger from 1.6.0 to 1.7.0.

Release notes

Sourced from @​aws-lambda-powertools/logger's releases.

v1.7.0

Summary

In this release we are excited to announce the first developer beta for the new Parameters utility 🎉. This new utility allows you to retrieve one or more parameter values from a range of AWS services, while also helping you reduce the amount of custom code needed to handle caching, transformations, and error handling.

The release also includes a new log level for Logger, support for high precision metrics in the Metrics utility, and a new behavior around missing segments in Tracer.

Parameters

Warning This utility is currently released as beta developer preview and is intended strictly for feedback and testing purposes and not for production workloads. The version and all future versions tagged with the -beta suffix should be treated as not stable. Up until before the General Availability release we might introduce significant breaking changes and improvements in response to customers feedback.

The Parameters utility provides high-level functions to retrieve one or multiple parameter values from AWS Systems Manager Parameter Store, AWS Secrets Manager, AWS AppConfig, Amazon DynamoDB, or your own parameter store.

Key features

  • Retrieve one or multiple parameters from the underlying provider
  • Cache parameter values for a given amount of time (defaults to 5 seconds)
  • Transform parameter values from JSON or base64 encoded strings
  • Bring Your Own Parameter Store Provider

Getting started

To start testing the utility, install it from npm using the @aws-lambda-powertools/parameters@1.7.0-beta alias.

In addition, you will need to add the AWS SDK client for the parameter store you are planning to use. The Parameters utility supports AWS SDK v3 for JavaScript only which allows the utility to be modular, and you to install only the SDK packages you need and keep your bundle size small:

  • SSM Parameters Store -> @aws-sdk/client-ssm
  • Secrets Manager -> @aws-sdk/client-secrets-manager
  • AppConfig -> @aws-sdk/client-appconfigdata
  • DynamoDB -> @aws-sdk/client-dynamodb @aws-sdk/util-dynamodb

Next, assign appropriate AWS Identity and Access Management (IAM) permissions to the Lambda function execution role of your Lambda function that allow retrieving parameters from the parameter store. You can see which permissions are needed for each action and store in the IAM Permissions section of the utility's docs.

Note In the section below we will use Secrets Manager as store to showcase different features of the Parameters utility. The same features are available for all other providers, as well as some others unique to each store. If you are interested in another store, skip to the utility docs.

Retrieving a single secret

To retrieve an individual parameter, the Parameters utility provides the getSecret function:

carbon

Adjusting cache TTL

By default, the retrieved value will be cached in-memory for 5 seconds. This cached value is used for subsequent invocations of the Lambda function until it expires. If you want to keep the value around longer, the Parameters utility allows you to adjust the time-to-live (TTL) via the maxAge argument:

carbon-2

If instead you want to make sure that the latest value is always retrieved and cache is skipped, you can use the forceFetch option:

carbon

... (truncated)

Changelog

Sourced from @​aws-lambda-powertools/logger's changelog.

1.7.0 (2023-03-20)

Bug Fixes

  • docs: typo in layer arn (bc5f7c9)

Features

  • logger: add silent log level to suppress the emission of all logs (#1347) (c82939e)
  • metrics: support high resolution metrics (#1369) (79a321b)
  • parameters: AppConfigProvider to return the last valid value when the API returns empty value on subsequent calls (#1365) (97339d9)
Commits
  • 6c7bf23 chore(release): v1.7.0 [skip ci]
  • 09fea8f chore: add private modifier to non utilities
  • 38f64b1 chore: add publishConfig modifier to non utilities
  • 1ca5068 chore: added parameters to docs navbar
  • d5e2aea chore(parameters): add package to release process (#1377)
  • 720d8a3 docs(parameters): write utility readme update main one (#1280)
  • a82fc3a refactor(tracer): log warning instead of throwing when segment is not found (...
  • 79a321b feat(metrics): support high resolution metrics (#1369)
  • 8a47e76 docs(parameters): add typedoc api docs (#1283)
  • 97339d9 feat(parameters): AppConfigProvider to return the last valid value when the A...
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by dreamorosi, a new releaser for @​aws-lambda-powertools/logger since your current version.


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 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 dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 27, 2023
github-actions[bot]
github-actions bot previously approved these changes Mar 27, 2023
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/modules/runner-binaries-syncer/lambdas/runner-binaries-syncer/aws-lambda-powertools/logger-1.7.0 branch from 8c37bc9 to 789fcf0 Compare March 30, 2023 20:28
github-actions[bot]
github-actions bot previously approved these changes Mar 30, 2023
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/modules/runner-binaries-syncer/lambdas/runner-binaries-syncer/aws-lambda-powertools/logger-1.7.0 branch from 789fcf0 to 4bb3a52 Compare March 30, 2023 20:42
github-actions[bot]
github-actions bot previously approved these changes Mar 30, 2023
Bumps [@aws-lambda-powertools/logger](https://github.com/awslabs/aws-lambda-powertools-typescript) from 1.6.0 to 1.7.0.
- [Release notes](https://github.com/awslabs/aws-lambda-powertools-typescript/releases)
- [Changelog](https://github.com/awslabs/aws-lambda-powertools-typescript/blob/main/CHANGELOG.md)
- [Commits](aws-powertools/powertools-lambda-typescript@v1.6.0...v1.7.0)

---
updated-dependencies:
- dependency-name: "@aws-lambda-powertools/logger"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/modules/runner-binaries-syncer/lambdas/runner-binaries-syncer/aws-lambda-powertools/logger-1.7.0 branch from 4bb3a52 to dd89738 Compare March 30, 2023 20:43
@npalm npalm merged commit 3ecb894 into main Mar 30, 2023
@npalm npalm deleted the dependabot/npm_and_yarn/modules/runner-binaries-syncer/lambdas/runner-binaries-syncer/aws-lambda-powertools/logger-1.7.0 branch March 30, 2023 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant