Details
-
Task
-
Resolution: Done
-
Major
-
None
-
2.7 GA
-
None
-
1
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
Description
Nowadays we issue events of type ProxyConfigs::AffectingObjectChangedEvent whenever proxy rules, proxies, backend api configs and backend apis are deleted. Sometimes we check if the owner of the deleted object still exists, but that's not enough. We should prevent those events from being issued whenever the provider account (or any object in between in the hierarchy) has been deleted or scheduled for deletion. There's no point in issuing that event in such cases.
Dev notes
Code is all here: https://github.com/3scale/porta/blob/f4c5468a6775c9f7e5a01ab0b92cfe5611554c6e/app/lib/proxy_config_affecting_changes.rb#L86
Add a safe-guard clause to return if the account is scheduled for deletion.