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.
What
Corrected the use of the wrong variable in the Quarantine & Unquarantine playbook when there are enough results from the Tanium API that pagination is required and we need to use the endCursor to get the next page of results.
Why
The use of the wrong variable caused the API call to be incorrect and return a 400 response indicating our graphQL body was not formatted properly.
How do I know this works?
I tested this myself both after manually fixing it in a playbook, and also by redeploying this updated template to confirm it works as expected.
How could I test this myself?
By doing the following: