We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Interacting with WAS scans is now done completely through the /was/v2/ endpoints. The /scans endpoint can no longer be used for WAS related things.
/was/v2/
/scans
Are there any plans for this wrapper to support WAS scan interactions?
The text was updated successfully, but these errors were encountered:
yes, we plan on supporting WASv2
Sorry, something went wrong.
@SteveMcGrath , is this fix/featrue released? If not, is there any workaround to get it done using current version?
No branches or pull requests
Interacting with WAS scans is now done completely through the
/was/v2/
endpoints. The/scans
endpoint can no longer be used for WAS related things.Are there any plans for this wrapper to support WAS scan interactions?
The text was updated successfully, but these errors were encountered: