You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The PyTenable library has an issue with the method name in exports API (it uses the wrong method name, tio.exports.was_vulns instead of tio.exports.was). Additionally, the tags parameter is invalid and should be removed, as the Tenable API V2 documentation for WAS Export Assets does not include a tag parameter (see https://developer.tenable.com/reference/export-assets-v2)
To Reproduce
Steps to reproduce the behavior:
Go to the PyTenable library's exports API implementation (tenable/io/exports/api.py).
Call the method tio.exports with a tags parameter.
Observe the error related to the incorrect method name and invalid tags parameter.
Refer to Tenable API v2 documentation for Export Assets, confirming no tag parameter exists.
Expected behavior
The method should be tio.exports.was instead of tio.exports.was_vulns, and the tags parameter should be removed from the function call to comply with the Tenable API documentation.
Screenshots
N/A
System Information (please complete the following information):
N/A
Describe the bug
The PyTenable library has an issue with the method name in
exports
API (it uses the wrong method name,tio.exports.was_vulns
instead oftio.exports.was
). Additionally, thetags
parameter is invalid and should be removed, as the Tenable API V2 documentation for WAS Export Assets does not include atag
parameter (see https://developer.tenable.com/reference/export-assets-v2)To Reproduce
Steps to reproduce the behavior:
exports
API implementation (tenable/io/exports/api.py
).tio.exports
with atags
parameter.tags
parameter.tag
parameter exists.Expected behavior
The method should be
tio.exports.was
instead oftio.exports.was_vulns
, and thetags
parameter should be removed from the function call to comply with the Tenable API documentation.Screenshots
N/A
System Information (please complete the following information):
N/A
Additional context
The error arises because the current implementation is not aligned with the API documentation for Tenable’s WAS Export Assets in version 2 (see https://developer.tenable.com/reference/export-assets-v2).
The text was updated successfully, but these errors were encountered: