[TRNT-4139] Update unversioned paths in API calls #3956
Merged
Conversation
This file contains hidden or 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
Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com> Use v2/clusters Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com> Use v2/clusters Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com> Fix Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com>
antgamdia
force-pushed
the
TRNT-4139-versioned-paths
branch
from
71f2c29 to
95a82e3
Compare
Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com>
Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com>
Signed-off-by: Antonio Gamez Diaz <antonio.gamez@suse.com>
vicenteqa
approved these changes
Jan 13, 2026
Contributor
Author
|
FTR, we triggered a flakiness analysis (see https://github.com/trento-project/web/actions/runs/20961496708), and tests seem to be consistently passing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
While debugging some CI issues in #3948, I noticed we had some old unversioned endpoints out there.
It should not affect anything, as the default behavior is to use the latest available API version, but, for the sake of consistency, I don't think it's a bad idea to reflect the proper API endpoints.
Related TRNT-4139
How was this tested?
CI
Additional information
When tests used unversioned
/api/collect, there was a 307 redirect, which added some latency and allowed thebeforeEachto work after having loaded the scenario with Photofinish.This PR adds a per-loaded-scenario
visitSelectedHost()call, ensuring the page always fetches fresh data after the scenario loads rather than relying on real-time event timing.