-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(custom_targets): handle embedded credentials, enable tests #188
Conversation
/build_test |
Workflow started at 11/23/2023, 11:51:16 AM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
38c128f
to
3bcd359
Compare
/build_test |
Workflow started at 11/27/2023, 5:13:25 PM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
3640144
to
856917f
Compare
This PR/issue depends on:
|
/build_test |
Workflow started at 11/28/2023, 10:14:22 AM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
856917f
to
e7f0e68
Compare
/build_test |
Workflow started at 11/28/2023, 10:39:38 AM. View Actions Run. |
CI build and push: All tests pass ✅ |
CI build and push: All tests pass ✅ |
e7f0e68
to
68896c7
Compare
…st target cleanup
…error cases (no ".data.result")
…eed to evaluate matching credentials for it for the first time
1a5f3a5
to
cea1f36
Compare
/build_test |
Workflow started at 12/15/2023, 2:40:39 PM. View Actions Run. |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
…ts (cryostatio#188)" This reverts commit 539940e.
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
Fixes #101
Related to #122
Based on #183
Depends on #183
Description of the change:
Re-enables the Custom Targets integration test that was ported over earlier. Along with this come some fixes to the initial 3.0 implementation so that the API responses match the pre-existing format, addition of handling of "embedded credentials" supplied with Custom Targets definitions, addition of handling to look up existing credentials from the keyring when opening a target connection, fixes to ensure that WebSocket messages are emitted in a more predictable order for clients to observe, some basic refactoring, and putting back the three instances of
vertx-fib-demo
like the old smoketest has.How to manually test:
./mvnw clean verify ; podman image prune -f
and ensure all tests pass./smoketest.bash -OXgtb
or whichever combination of flags you likeservice:jmx:rmi:///jndi/rmi://vertx-fib-demo-2:9094/jmxrmi
. In the latest smoketest script,vertx-fib-demo-n
andsample-app-n
(n: [1, 2, 3]
) are basically synonymous - both forms are resolvable hostnames from the perspective of the cryostat3 container.vertx-fib-demo-2:9094
andvertx-fib-demo-3:9095
are free to use as custom targets, the other URLs will be automatically discovered by JDP and the samples' Agent instances.With
service:jmx:rmi:///jndi/rmi://vertx-fib-demo-2:9094/jmxrmi
:admin:adminpass123
in the form, test the connection again. It should succeed.user:password
, test again. It should still succeed.user:password
and create the custom target. This should succeed and some notifications should appear. You will be brought back to the Topology view, which depends on GraphQL ([Story] GraphQL #11), so don't worry about that view being broken for now.admin:adminpass123
combination.With
service:jmx:rmi:///jndi/rmi://vertx-fib-demo-3:9095/jmxrmi
:With
service:jmx:rmi:///jndi/rmi://cryostat3:9091/jmxrmi
:onstart
recording that is already present.Note: deleting a Custom Target is only exposed in the UI via the Topology view, so there is no way to undo this graphically yet. You can either tear down and restart the smoketest to get a fresh slate, or you can use curl/HTTPie and delete the custom target directly via the API: