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

[Tenable Vuln Management] : last_scan_target attribute inconsistent presence in API response should be handled gracefully #3542

Closed
flavienSindou opened this issue Mar 3, 2025 · 1 comment · Fixed by #3547
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@flavienSindou
Copy link
Contributor

No description provided.

@flavienSindou flavienSindou changed the title [Tenable vuln management] : last_scan_target attribute is not always return by the API [Tenable Vuln Management] : last_scan_target attribute inconsistent presence in API response should be handled gracefully Mar 3, 2025
@flavienSindou flavienSindou self-assigned this Mar 3, 2025
@flavienSindou flavienSindou added bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. labels Mar 3, 2025
flavienSindou added a commit that referenced this issue Mar 4, 2025
…t presence in API response should be handled gracefully (#3542)

Co-authored-by: Pauline Eustachy <[email protected]>
@flavienSindou flavienSindou added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 4, 2025
@flavienSindou flavienSindou added this to the Release 6.5.4 milestone Mar 4, 2025
@flavienSindou
Copy link
Contributor Author

Other response attributes seem affected :
#3574

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
1 participant