-
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(graphql): add top-level query for environmentNodes #308
Conversation
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
77649fa
to
e6c3388
Compare
/build_test |
You do not have permission to run the /build_test command. Please ask @cryostatio/reviewers |
/build_test |
Workflow started at 2/29/2024, 12:05:18 AM. View Actions Run. |
CI build and push: All tests pass ✅ (JDK21) |
CI build and push: All tests pass ✅ (JDK17) |
ba3cd8a
to
fc7f230
Compare
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
Based on: #294
Description of the change:
This change allows an environment variable to be configured so that...
Motivation for the change:
This change is helpful because users may want to...
How to manually test:
$ http --follow -v --auth=user:pass :8080/api/v3/graphql/schema.graphql
and ensure new schema contains top-level query and subqueries.http --follow -v --auth=user:pass :8080/api/v2.2/graphql query='query { environmentNodes(filter: { nodeType: "Realm" }) { id name nodeType labels { key value } children { id name nodeType labels { key value } } } }'
change the filter to filter by name i.ehttp --follow -v --auth=user:pass :8080/api/v2.2/graphql query='query { environmentNodes(filter: { name: "JDP" }) { id name nodeType labels { key value } children { id name nodeType labels { key value } } } }'
. If a match is not found you should get empty array forenvironmentNodes
nodeType