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.

Sign up for GitHub

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

Jump to bottom

pools do not have to be unique anymore #169

Closed
bavarianbidi opened this issue Sep 25, 2024 · 1 comment
Closed

pools do not have to be unique anymore #169

bavarianbidi opened this issue Sep 25, 2024 · 1 comment
Milestone
support for garm ...

Comments

@bavarianbidi
Copy link
Member

What is the feature you would like to have?

as pools do not have to be unique anymore, we can't "adopt" existing pools with the same spec by just reflecting the status-uuid back to the CR.

We should remove the entire adoption for

  • pools

TBD:

  • org/repo/enterprise

Anything else you would like to add?

No response
@bavarianbidi bavarianbidi added this to the support for garm > 0.1.4 milestone Sep 25, 2024
@bavarianbidi bavarianbidi mentioned this issue Oct 21, 2024
Merged
14 tasks
@bavarianbidi
Copy link
Member Author

duplicate of #139

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
support for garm > 0.1.4
Development

No branches or pull requests
1 participant
@bavarianbidi