Skip to content

Remove deprecated GlobalAccount #161

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

Open
GenosseOtt opened this issue Apr 30, 2025 · 1 comment
Open

Remove deprecated GlobalAccount #161

GenosseOtt opened this issue Apr 30, 2025 · 1 comment
Labels
good first issue New to this repo? This is a good place to start

Comments

@GenosseOtt
Copy link
Contributor

GenosseOtt commented Apr 30, 2025

Context

As we have deprecated GlobalAccount some time ago, lets remove completely to keep docs and end user complexity as little as possible

Acceptance criteria

  • Remove GlobalAccount ressource completly
  • Upgrade path: Ensure user moves GlobalAccount to ProviderConfig
  • Remove from all end user guides
  • CRD Browser - leave? How to handle? @sdischer-sap
@sdischer-sap
Copy link
Member

sdischer-sap commented May 2, 2025

I would love to do that, but I'am afraid this would break the provider upgrade process if the user still has CRs using it.

So in order to do that we need to verify how the upgrade behaves here and if it can be resolves in a clean way once it failed. If the user would just need to remove all CRs and the upgrade would unblock itself than maybe thats still okay (with proper documentation and announcements of course).

So I would make that one a spike first of all and spend some time on experimenting with an upgrade in that test. Maybe that can be part of #156

Lets discuss in refinement

@GenosseOtt GenosseOtt added the good first issue New to this repo? This is a good place to start label May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue New to this repo? This is a good place to start
Projects
None yet
Development

No branches or pull requests

2 participants