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

fix cascading deletion #746

Closed
wants to merge 1 commit into from

Conversation

MStokluska
Copy link
Contributor

Fix cascading deletion issue when provider account secret is not found

Verification:
Create tenant
Create backend associated with that tenant
Create product associated with that tenant
Remove tenant
Confirm product and backend CRs are deleted as well

@MStokluska MStokluska force-pushed the fix-cascading-deletion branch from bc23726 to 323db95 Compare May 6, 2022 07:16
@codeclimate
Copy link

codeclimate bot commented May 6, 2022

Code Climate has analyzed commit 323db95 and detected 2 issues on this pull request.

Here's the issue category breakdown:

Category Count
Complexity 2

View more on Code Climate.

@eguzki
Copy link
Member

eguzki commented May 6, 2022

I was looking going to implement something very similar. Then I realized that in the backend controller, if the secret is not found, then the product CR references to that backend are not deleted.

I refactored a bit to decouple backend deletion from 3scale and product reference cleaning.

Let me know what you think: #747

@MStokluska
Copy link
Contributor Author

closing in favor of #747

@MStokluska MStokluska closed this May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants