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

test: fix error message in 'validate' #7920

Merged
merged 1 commit into from
Mar 5, 2025

Conversation

valerena
Copy link
Contributor

@valerena valerena commented Mar 5, 2025

cfn-lint changed their message when a Lambda runtime is deprecated 1

From Check if EOL Lambda Function Runtimes are used
To Validate if lambda runtime is deprecated

And also using nodejs16.x changed from a warning (W2531) to an error (E2531)

Also, removed some extra escape characters that were not required.

Which issue(s) does this change fix?

Why is this change necessary?

How does it address the issue?

What side effects does this change have?

Mandatory Checklist

PRs will only be reviewed after checklist is complete

  • Add input/output type hints to new functions/methods
  • Write design document if needed (Do I need to write a design document?)
  • Write/update unit tests
  • Write/update integration tests
  • Write/update functional tests if needed
  • make pr passes
  • make update-reproducible-reqs if dependencies were changed
  • Write documentation

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

`cfn-lint` changed their message when a Lambda runtime is deprecated [1]

From `Check if EOL Lambda Function Runtimes are used`
To `Validate if lambda runtime is deprecated`

And also using nodejs16.x changed from a warning (W2531) to an error (E2531)

[1]: aws-cloudformation/cfn-lint@31783ca#diff-3e96ba21727bba3d7bfb0c5c235a0cbc45eca97819429104d7ff9fbec8aa05b2
@valerena valerena requested a review from a team as a code owner March 5, 2025 16:08
@seshubaws
Copy link
Contributor

just curious, is there a ticket associated with this? Or did we just see the change?

@valerena
Copy link
Contributor Author

valerena commented Mar 5, 2025

just curious, is there a ticket associated with this? Or did we just see the change?

I noticed it was the reason why some of our AppVeyor integration tests were failing

@valerena valerena added this pull request to the merge queue Mar 5, 2025
Merged via the queue into aws:develop with commit 3e67c80 Mar 5, 2025
52 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants