fix(hub): ticket appears even cancelled #11662
Conversation
remove cache for tickets ref: MANAGER-13862 Signed-off-by: Maxime Bajeux <maxime.bajeux.ext@corp.ovh.com>
There was a problem hiding this comment.
question: Does the 2API supports or forwards the headers to the underlying APIv6 call?
There was a problem hiding this comment.
On the 2api side, cache is handle for all the hub and it seems we can't override the behaviour without refactoring for all the hub. I tested and it seems the fix works well. Do you have another solution in head ?
There was a problem hiding this comment.
Seems there is no cache between apiV6 and 2api, so normally I think we not need to forward the headers to api V6 because the cache exists only between the 2api and the manager. About the performance cost, obviously that costs one API call each time the service is call. To reduce the performance issue, we could get only the two latest tickets from API instead of getting all and truncate into the 2api, like in the bff. But this is something that will be resolved once the bff is in production.
try to refresh cache when cancel ref: MANAGER-13862 Signed-off-by: Maxime Bajeux <maxime.bajeux.ext@corp.ovh.com>
MaximeBajeux
force-pushed
the
fix/MANAGER-13862
branch
from
877b76e
to
6028d8a
Compare
This reverts commit 6028d8a. ref: fix/MANAGER-13862
|
masterDescription
Remove cache for tickets in dashboard
Related