Skip to content
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

Update to support for WAS API V2 #310

Open
d0n601 opened this issue May 21, 2021 · 2 comments
Open

Update to support for WAS API V2 #310

d0n601 opened this issue May 21, 2021 · 2 comments
Labels
backlog Issue Backlog
Milestone

Comments

@d0n601
Copy link

d0n601 commented May 21, 2021

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?

@levwais levwais added the follow-up label for items that requires follow-up internally label Jun 23, 2021
@SteveMcGrath
Copy link
Contributor

yes, we plan on supporting WASv2

@SteveMcGrath SteveMcGrath added enhancement New features/functionality backlog Issue Backlog and removed follow-up label for items that requires follow-up internally enhancement New features/functionality labels Sep 22, 2021
@SteveMcGrath SteveMcGrath added this to the 1.5 milestone Sep 28, 2021
@mukilarasan-ravi
Copy link

mukilarasan-ravi commented May 4, 2022

@SteveMcGrath , is this fix/featrue released? If not, is there any workaround to get it done using current version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Issue Backlog
Projects
None yet
Development

No branches or pull requests

4 participants