Fix resource deletions not propagating through service instances #2196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix resource deletions not propagating through service instances
The issue or feature being addressed
Other instances were not picking up the change when deleting a resource, such as an Agent. For example, the Agent would still appear in the User Portal after deleting it in the Management Portal, or it would reappear in the Management Portal when hitting a different instance of the Management API.
Details on the issue fix or feature implementation
Adds custom equality operators to the
ResourceReference
class and evaluates in-memory resource references against the list of persisted references, updating the in-memory reference if it is different.Confirm the following
Note
Instead of adding
X
's inside the checkboxes you wish to check above, first submit the PR, then check the boxes in the rendered description.