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

Removing relation of a consumed resource that has no relation name is not possible #707

Open
llorentelemmc opened this issue Oct 25, 2023 · 0 comments · May be fixed by #709
Open

Removing relation of a consumed resource that has no relation name is not possible #707

llorentelemmc opened this issue Oct 25, 2023 · 0 comments · May be fixed by #709
Labels

Comments

@llorentelemmc
Copy link
Contributor

llorentelemmc commented Oct 25, 2023

Setup: A resource with a related, consumed resource

Reproduce:

  1. Remove the related resource

If you add a RelationName, the related resource is successfully removed. If there is no RelationName, the related resource is not removed.

The related resource should also be removable without relation name.

@llorentelemmc llorentelemmc self-assigned this Oct 26, 2023
@llorentelemmc llorentelemmc added this to the Version 1.17.32 milestone Oct 26, 2023
@llorentelemmc llorentelemmc linked a pull request Oct 26, 2023 that will close this issue
@llorentelemmc llorentelemmc linked a pull request Oct 26, 2023 that will close this issue
@llorentelemmc llorentelemmc changed the title Removing a relation of a consumed resource that has no relation name is not possible Removing relation of a consumed resource that has no relation name is not possible Oct 27, 2023
@llorentelemmc llorentelemmc removed this from the Version 1.17.32 milestone Nov 1, 2023
@yvespp yvespp added this to the Version 1.17.33 milestone Nov 14, 2023
@llorentelemmc llorentelemmc removed their assignment Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants