Skip to content

Conversation

@kthota-g
Copy link
Contributor

Description

Introduces support for Database backed Push Notification Config Store.

Push Notification Config persisted to the database table gets encrypted when encryption_key param is set for the DatabasePushNotificationConfigStore.

Usage:

httpx_client = httpx.AsyncClient()
 engine = create_async_engine(
            "sqlite+aiosqlite:///file::memory:?cache=shared",
            echo=False
        )

push_config_store = DatabasePushNotificationConfigStore(engine=engine,
                    encryption_key=Fernet.generate_key()) 
push_sender = BasePushNotificationSender(
    httpx_client=httpx_client,
    config_store=push_config_store)

 request_handler = DefaultRequestHandler(
            agent_executor=CurrencyAgentExecutor(),
            task_store=DatabaseTaskStore(engine=engine),
            push_config_store=push_config_store,
            push_sender=push_sender)

@kthota-g kthota-g requested a review from a team as a code owner July 11, 2025 20:43
@kthota-g kthota-g changed the title Kthota/sql push feat: Support for Database based Push Config Store Jul 11, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @kthota-g, I'm Gemini Code Assist1! 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 significantly enhances the persistence and security of push notification configurations by introducing a robust database-backed storage solution. It allows for the secure storage of configuration data in various SQL databases, with an added layer of optional encryption for sensitive information.

Highlights

  • Database-backed Push Notification Config Store: Introduced a new DatabasePushNotificationConfigStore that leverages SQLAlchemy to persist push notification configurations in a database. This replaces or complements in-memory storage, providing durability and scalability.
  • Optional Data Encryption: The DatabasePushNotificationConfigStore now supports optional encryption of sensitive config_data using cryptography.fernet. If an encryption_key is provided during initialization, data is encrypted before being written to the database and decrypted upon retrieval.
  • Configurable Database Model: A new PushNotificationConfigMixin and create_push_notification_config_model function were added to src/a2a/server/models.py, allowing the database table for push notification configurations to be named dynamically, enhancing flexibility for different deployment scenarios.
  • Comprehensive Test Coverage: Extensive new tests have been added for the DatabasePushNotificationConfigStore, covering CRUD operations, initialization idempotency, and critical encryption/decryption scenarios across various database backends (SQLite, PostgreSQL, MySQL).
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 is currently in preview and 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 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a DatabasePushNotificationConfigStore for persisting push notification configurations, with optional encryption using the cryptography library. The implementation is well-structured, with good error handling and comprehensive tests.

I've identified a correctness issue in the decryption logic that could lead to an unhandled exception, and a couple of issues in the tests where they don't correctly test the intended functionality. My review includes suggestions to fix these issues.

Overall, this is a solid feature addition.

@kthota-g kthota-g marked this pull request as draft July 11, 2025 21:12
@kthota-g kthota-g marked this pull request as ready for review July 11, 2025 21:48
@kthota-g kthota-g changed the title feat: Support for Database based Push Config Store feat: Support for Database based Push Config Store [DO NOT MERGE] Jul 14, 2025
@kthota-g kthota-g changed the title feat: Support for Database based Push Config Store [DO NOT MERGE] feat: Support for Database based Push Config Store Jul 14, 2025
@holtskinner holtskinner merged commit e5d99ee into main Jul 15, 2025
8 checks passed
@holtskinner holtskinner deleted the kthota/sql_push branch July 15, 2025 16:10
holtskinner pushed a commit that referenced this pull request Jul 17, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.13](v0.2.12...v0.2.13)
(2025-07-17)


### Features

* Add `get_data_parts()` and `get_file_parts()` helper methods
([#312](#312))
([5b98c32](5b98c32))
* Support for Database based Push Config Store
([#299](#299))
([e5d99ee](e5d99ee))
* Update A2A types from specification 🤖
([#319](#319))
([18506a4](18506a4))


### Bug Fixes

* Add Input Validation for Task IDs in TaskManager
([#310](#310))
([a38d438](a38d438))
* Add validation for empty artifact lists in `completed_task`
([#308](#308))
([c4a324d](c4a324d))
* Handle readtimeout errors.
([#305](#305))
([b94b8f5](b94b8f5)),
closes [#249](#249)


### Documentation

* Update Documentation Site Link
([#315](#315))
([edf392c](edf392c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants