mp: Added no-ssl verification in dev-env deploy

[lemanczykp]

mp tool: Optional disabling ssl verification for dev-env push

Description

Disables ssl when pushing the integration to a development env. This is usefull for localhost deployments.
Example usage:

mp dev-env login --no-ssl
mp dev-env push tools --no-ssl

When using this param the tools throws new warnings

Checklist:

Please ensure you have completed the following items before submitting your PR.
This helps us review your contribution faster and more efficiently.

General Checks:

• I have read and followed the project's contributing.md guide.
• My code follows the project's coding style guidelines.
• I have performed a self-review of my own code.
• My changes do not introduce any new warnings.
• My changes pass all existing tests.
• I have added new tests where appropriate to cover my changes. (If applicable)
• I have updated the documentation where necessary (e.g., README, API docs). (If applicable)

Open-Source Specific Checks:

• My changes do not introduce any Personally Identifiable Information (PII) or sensitive customer data.
• My changes do not expose any internal-only code examples, configurations, or URLs.
• All code examples, comments, and messages are generic and suitable for a public repository.
• I understand that any internal context or sensitive details related to this work are handled separately in internal systems (Buganizer for Google team members).

For Google Team Members and Reviewers Only:

• I have included the Buganizer ID in the PR title or description (e.g., "Internal Buganizer ID: 123456789" or "Related Buganizer: go/buganizer/123456789").
• I have ensured that all internal discussions and PII related to this work remain in Buganizer.
• I have tagged the PR with one or more labels that reflect the pull request purpose.

---

[gemini-code-assist]

Summary of Changes

Hello @lemanczykp, 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 introduces a new --no-ssl flag for the mp dev-env login and mp dev-env push commands. This enhancement provides developers with the flexibility to disable SSL certificate verification when interacting with development environments, which is especially beneficial for local deployments and testing where standard SSL certificates may not be configured or are self-signed. The underlying BackendAPI has been updated to support this new verification control.

Highlights

• New --no-ssl option for mp dev-env login: Introduced a new --no-ssl option for the mp dev-env login command, allowing users to bypass SSL certificate verification when authenticating to a development environment. This is particularly useful for localhost setups where self-signed or no SSL certificates might be in use.
• New --no-ssl option for mp dev-env push: Added a --no-ssl option to the mp dev-env push command, enabling the optional disabling of SSL verification during the deployment of integrations to a development environment. This streamlines the deployment process for local development and testing.
• BackendAPI class modification: The BackendAPI class constructor now accepts a verify_ssl boolean parameter. This parameter is used to configure the requests.Session object's verify attribute, allowing programmatic control over SSL certificate verification for all subsequent HTTP requests made by the API client.

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

[gemini-code-assist]

Code Review

This pull request introduces a --no-ssl flag to the dev-env login and dev-env push commands, allowing users to disable SSL certificate verification. This is a useful feature for local development environments. The implementation correctly passes the flag down to the BackendAPI to control the requests session's verification behavior.

My review includes a few suggestions to improve the code:

• Refactoring the BackendAPI instantiation in both login and push commands to reduce code duplication.
• Suppressing the InsecureRequestWarning that requests issues when SSL verification is disabled, which will improve the user experience as mentioned in the PR description.

Overall, the changes are well-implemented and address the intended goal.

[doriaviram]

Hey, do you want to fix the lint issues ?

[lemanczykp]

@doriaviram Hi, this feature is mostly for ease of local development and was not requested. The lint issues require a bit of rework and retest for which I recently did not have "spare" time. Will try to wrap it during this or next week.

[lemanczykp]

@doriaviram Hi, streamlined handling of localhost a bit so it does not require separate parameter for TLS disabling but now it does it on its own. Let me know if this is ok for you.