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

Backport of provider meta: don't return providers with invalid names into v1.9 #35849

Merged
merged 2 commits into from
Oct 16, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Backport

This PR is auto-generated from #35842 to be assessed for backporting due to the inclusion of the label 1.9-backport.

The below text is copied from the body of the original PR.


This PR updates the parsing of the provider_meta blocks so that providers with invalid names aren't returned. This prevents a crash that occurs later when the names are parsed, and doesn't affect behaviour otherwise as the diagnostic explaining the error is still returned.

Fixes #35835

Target Release

1.9.x

Draft CHANGELOG entry

BUG FIXES

  • Prevent crash when loading provider_meta blocks with invalid names.

Overview of commits

@github-actions github-actions bot force-pushed the backport/liamcervante/35835/cheaply-main-beagle branch from 886159d to df5a122 Compare October 14, 2024 08:37
@liamcervante liamcervante merged commit 6325551 into v1.9 Oct 16, 2024
6 checks passed
@liamcervante liamcervante deleted the backport/liamcervante/35835/cheaply-main-beagle branch October 16, 2024 06:47
Copy link
Contributor Author

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

Copy link
Contributor Author

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant