client: Consistently accept --debug

[cgwalters]

To debug things.

[gemini-code-assist]

Summary of Changes

Hello @cgwalters, 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 standardizes the handling of common command-line options, specifically --debug and --insecure, across various client commands. By introducing a shared options structure, it ensures consistency in how these flags are processed and passed to the underlying image proxy configuration, making the client application more robust and easier to extend.

Highlights

• Introduction of CommonOpts struct: A new CommonOpts struct has been introduced to encapsulate common command-line options like --debug and --insecure.
• Consistent --debug flag: The --debug flag is now consistently accepted across client commands by being part of the new CommonOpts struct and propagated to the ImageProxyConfig.
• Refactoring of option handling: The logic for converting command-line options to ImageProxyConfig has been refactored into a CommonOpts::to_config method, improving code reusability and maintainability.

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

[gemini-code-assist]

Code Review

This pull request refactors common command-line options like --debug and --insecure into a CommonOpts struct, which is a good approach to reduce code duplication and improve consistency. The changes correctly apply these common options to most subcommands.

My review includes a suggestion to improve the implementation of the configuration conversion function for better readability and idiomatic Rust. I also noticed that one of the subcommands, get-blob-raw, does not yet use the new common options, which I've pointed out to ensure the change is applied consistently as intended.

[gemini-code-assist]

Great job refactoring the common options into CommonOpts and applying it to GetBlobOpts.

However, it seems the get-blob-raw subcommand, which also uses GetBlobOpts, was missed. The get_blob_raw function still calls ImageProxy::new().await? and doesn't use the new common options from GetBlobOpts.

To ensure the --debug and --insecure flags work consistently across all subcommands as the PR title suggests, you should update get_blob_raw to create the proxy with the configuration, similar to what you've done for get_blob:

async fn get_blob_raw(o: GetBlobOpts) -> Result<()> {
    let config = o.common.to_config();
    let proxy = containers_image_proxy::ImageProxy::new_with_config(config).await?;
    // ...
}