Create push notification config returns no id on database-backed stores

[ConnorMoss02]

What happens

Creating a push notification config against a database-backed server returns a config with no id. Reading it back with that id raises InvalidParamsError.

create returned id = ''
get FAILED -> InvalidParamsError: Validation failed

The same calls against the in-memory store return id='task-123' and the get succeeds.

Why

on_create_task_push_notification_config returns the caller's request object rather than what the store persisted (default_request_handler.py:556, default_request_handler_v2.py:394).

Both stores default an empty id to the task id, on different objects:

• inmemory_push_notification_config_store.py:51 sets it on the caller's object, so return params carries it.
• database_push_notification_config_store.py:292 copies first and sets it on the copy, so params never gets it.

The store holds the right id either way; only the response differs.

Version

main @ d55a3d3

[rohityan]

Hi @ConnorMoss02 , thanks for reporting this. You're observation of why its happening is correct.
While the PR #1236 is reviewed, you could work around this behavior at the application level by pre-populating the config ID. Simply pass id=task.id when instantiating TaskPushNotificationConfig. The server will receive a pre-populated id and never trigger the default assignment branch in the store.