fix: wait for the alias to be processed in the API layer #690
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For objects with aliases, like agents, if the alias is created or updated, the API may return stale data because the controller hasn't processed the object yet. This change adds a mechanism for the API layer to ensure that the alias controller has processed the object. Signed-off-by: Donnie Adams <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For objects with aliases, like agents, if the alias is created or updated, the API may return stale data because the controller hasn't processed the object yet. This change adds a mechanism for the API layer to ensure that the alias controller has processed the object.
Issue: #634