Skip to content

Missing significant newsfragment for standard provider #44482

Closed

Description

@Lee-W

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

Activity

  1. added
    kind:bugThis is a clearly a bug
    needs-triagelabel for new issues that we didn't triage yet
    and removed
    needs-triagelabel for new issues that we didn't triage yet
    on Nov 29, 2024
  2. potiuk commented on Nov 29, 2024

    @potiuk
    Member

    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.

  3. Lee-W commented on Jan 13, 2025

    @Lee-W
    MemberAuthor

    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?

  4. self-assigned this
    on Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions