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

Missing significant newsfragment for standard provider #44482

Closed
2 tasks done
Lee-W opened this issue Nov 29, 2024 · 2 comments · Fixed by #45740
Closed
2 tasks done

Missing significant newsfragment for standard provider #44482

Lee-W opened this issue Nov 29, 2024 · 2 comments · Fixed by #45740
Assignees
Labels
kind:bug This is a clearly a bug kind:documentation

Comments

@Lee-W
Copy link
Member

Lee-W commented Nov 29, 2024

What do you see as an issue?

I think this could be considered a breaking change as users won't be able to import these operators in the old way. These are the prs I notice

#41564
#42506
#42794
#43608
#43890
#44053
#44288

Solving the problem

No response

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Lee-W Lee-W added kind:bug This is a clearly a bug kind:documentation needs-triage label for new issues that we didn't triage yet and removed needs-triage label for new issues that we didn't triage yet labels Nov 29, 2024
@potiuk
Copy link
Member

potiuk commented Nov 29, 2024

BTW. The idea is that we redirect old imports to new standard provider automatically when we complete the provider move, but yes, newsfragment for that one will be needed.

@Lee-W
Copy link
Member Author

Lee-W commented Jan 13, 2025

The idea is that we redirect old imports to new standard provider automatically when we complete the provider move

I guess it means we do not need a migration rule for this then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug This is a clearly a bug kind:documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants