[ANY.RUN]: Update authorization workflow

[semayellow]

ANY.RUN integrations update

Description

AnyRun TI Feeds

• Updated documentation and configs for using API key instead of Basic auth token.
• Updated SDK version.

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 @semayellow, 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 focuses on modernizing the ANY.RUN Threat Intelligence Feeds integration by updating its authentication mechanism from a Basic token to a more secure API key. This involves upgrading the anyrun-sdk dependency and adjusting all relevant configuration settings and documentation to ensure seamless adoption of the new authentication flow, thereby enhancing the integration's security and maintainability.

Highlights

• Authentication Method Update: The ANY.RUN TI Feeds integration has been updated to utilize an API key for authentication, replacing the previous Basic token method. This change is reflected in the configuration parameters and the underlying code.
• SDK and Integration Version Bump: The anyrun-sdk dependency has been upgraded to version 1.12.11, and the overall integration version has been incremented from 2.0 to 3.0 to reflect these significant updates.
• Configuration Parameter Renaming: User-facing configuration parameters and internal references have been renamed from 'ANYRUN TI Feeds Basic token' to 'ANYRUN TI Feeds API key' to align with the new authentication mechanism.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

The pull request successfully updates the ANY.RUN integration to utilize an API key for authorization instead of a basic token, and also updates the SDK version. The changes are consistently applied across the configuration files, Python code, and dependency specifications. A minor issue was identified in the release notes regarding a placeholder ticket number.

[github-actions]

❌ Marketplace Validation Failed

Click to view the full report

---

Validation Report

🧩 Integrations

Pre-Build Stage

anyrun_ti_feeds

Validation Name	Details
⚠️ Uv Lock	Error happened while executing a command: uv lock --check: Using CPython 3.11.14 interpreter at: /opt/hostedtoolcache/Python/3.11.14/x64/bin/python Resolved 61 packages in 1.37s The lockfile at uv.lock needs to be updated, but --check was provided. To update the lockfile, run uv lock.

[AmitJ98]

Hi @semayellow before merging please resolve (accept or close) gemini comments and run uv lock in your project (see the validation report - uv lock validation failded)

[github-actions]

❌ Marketplace Validation Failed

Click to view the full report

---

Validation Report

🧩 Integrations

Pre-Build Stage

anyrun_ti_feeds

Validation Name	Details
⚠️ Uv Lock	Error happened while executing a command: uv lock --check: Using CPython 3.11.14 interpreter at: /opt/hostedtoolcache/Python/3.11.14/x64/bin/python Resolved 61 packages in 1.09s The lockfile at uv.lock needs to be updated, but --check was provided. To update the lockfile, run uv lock.

[semayellow]

Hi @semayellow before merging please resolve (accept or close) gemini comments and run uv lock in your project (see the validation report - uv lock validation failded)

Hi @AmitJ98, it's done.