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

update auth-at-edge semantic version to latest 2.1.5 #480

Merged
merged 1 commit into from
May 25, 2023

Conversation

dlpzx
Copy link
Contributor

@dlpzx dlpzx commented May 25, 2023

Feature or Bugfix

  • Bugfix

Detail

Custom resources created by the cloudfront-authorization-at-edge application used in data.all use node12 for the version of the application previously used (2.0.4). By upgrading to the latest version (2.1.5) the Lambda custom resources used also use node14 at runtime.

After upgrading the semantic version, I performed the following tests:

  • upgrade a pre-existing deployment (Lambdas node12) and check that the runtime has been updated to node14. See screenshot below.
  • open userguide (where auth at edge is used) in pre-existing deployment
  • execute GraphQL APIs in pre-existing deployment
  • execute ES APIs in pre-existing deployment

image

  • deploy data.all from scratch and check that the Lambdas deployed use node14
  • open userguide (where auth at edge is used) in new deployment
  • execute GraphQL APIs in new deployment
  • execute ES APIs in new deployment

image

Relates

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@dlpzx dlpzx marked this pull request as ready for review May 25, 2023 10:06
@dlpzx dlpzx requested a review from nikpodsh May 25, 2023 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants