Add log_level option for adk run CLI

[vadakattu]

Added log_level option for adk run CLI, inline with other CLI capabilities

Problem:
The CLI option was overlooked for this entry point & the logs utility lot_to_tmp_folder was not receiving a log level argument.

Solution:
Cloned the click option as defined for other entry points, added function argument, and passed to logging utility function

Checklist

• I have read the CONTRIBUTING.md document.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have manually tested my changes end-to-end.
• Any dependent changes have been merged and published in downstream modules.

[gemini-code-assist]

Summary of Changes

Hello @vadakattu, 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!

This pull request addresses an oversight in the adk run CLI command by adding a --log_level option, bringing it in line with other CLI capabilities. The change allows users to control the logging verbosity directly from the command line, ensuring that the logging utility log_to_tmp_folder properly utilizes the specified level for more consistent and configurable logging behavior across the application.

Highlights

• CLI Log Level Option: Introduced a new --log_level option for the adk run CLI command, allowing users to specify the desired logging verbosity.
• Logging Utility Integration: Ensured that the logs.log_to_tmp_folder utility now correctly receives and applies the log_level argument provided via the CLI.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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. ↩

[adk-bot]

Response from ADK Triaging Agent

Hello @vadakattu, thank you for creating this PR!

Could you please include a testing plan section in your PR to talk about how you will test? This will save time for PR review.

In addition, could you please provide logs or screenshot after the fix is applied? This information will help reviewers to review your PR more efficiently. Thanks!

[gemini-code-assist]

Code Review

This pull request adds a --log_level option to the adk run command, which is a good enhancement for consistency with other CLI commands. The implementation is straightforward and mostly correct. I have one suggestion to improve consistency in how the log level is passed to the utility function, aligning it with the pattern used elsewhere in the file.

[ryanaiagent]

Hi @vadakattu ,Thank you for your contribution through this pull request! This PR has merge conflicts that require changes from your end. Could you please rebase your branch with the latest main branch to address these? Once this is complete, please let us know so we can proceed with the review.