test(itest): updated UploadRecordingTest to handle the redirects to V3 endpoints #150
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.
Welcome to Cryostat3! 👋
Before contributing, make sure you have:
main
branch[chore, ci, docs, feat, fix, test]
To recreate commits with GPG signature
git fetch upstream && git rebase --force --gpg-sign upstream/main
Related to #42
Description of the change:
Created new methods to handle the redirects to new V3 endpoints for the UploadRecordingTest
Notes: It will fail during the create recording ("/api/v1/targets/%s/recordings") as it is expecting 201 and it is currently is returning 200 (updated Recordings to return 201)
The original test to delete recording was expecting 200 code, but I think that the current 204 makes more sense.
Motivation for the change:
vertx does not follow redirects for non GET and HEAP methods
How to manually test:
mvn package