add CLI support for alerts summaries scans and following over time

[epalhares-tenchi]

Description

This PR adds two new commands to the CLI, reflecting recent additions to the SDK:

---

get_alerts_summaries_scans

• Calls: POST /alerts/summaries/scans
• Flags:
  • --organization-id (required)
  • --scan-target-ids (optional, list)
  • --days (optional, default = 7)

---

get_following_alerts_over_time

• Calls: POST /alerts/summaries/following/resolvedovertime
• Flags:
  • --organization-id (required)
  • --following-ids (optional, list)
  • --severities (optional, list)
  • --dates (optional, list of YYYY-MM-DD)

---

Both commands support JSON output and follow the SDK structure.
This update is part of the ongoing SDK/CLI sync based on the

[gemini-code-assist]

Summary of Changes

Hello @epalhares-tenchi, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've introduced two new CLI commands to align with recent additions to the SDK, enabling users to fetch alert summaries for scans and track following alerts over time directly from the command line. This update enhances the CLI's capabilities by exposing more data retrieval functionalities previously only available via the SDK.

Highlights

• New CLI Command: get_alerts_summaries_scans: I've added a new CLI command, alerts_scans, which wraps the client.get_alerts_summaries_scans SDK call. This command supports organization-id (required), scan-target-ids (optional list), and days (optional, defaulting to 7).
• Updated CLI Command: get_following_alerts_over_time: I've updated the existing summary_following_alerts_over_time command to correctly call client.get_following_alerts_over_time instead of client.get_alerts_over_time. This command continues to accept organization-id, following-ids, severities, and dates.
• SDK Version Bump: The zanshinsdk dependency has been bumped from version 2.1.9 to 2.1.10 across the project's dependency management files (pyproject.toml and poetry.lock).

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces two new CLI commands, get_alerts_summaries_scans and get_following_alerts_over_time, by updating the zanshinsdk dependency and adding corresponding functions in src/bin/summary.py. The changes are well-structured and align with the existing code. I have one suggestion to improve the clarity of a help message for one of the new command's options.