temporalio / temporalio/temporal

Ability to update schedule memo via Python SDK

Open
#5,510 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement schedules
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.
Client,create_schedule allows a memo to be created on a schedule. Most schedule fields can be updated by calling ScheduleHandle.update, but it does not seem to allow the update of a memo with ScheduleUpdateInput/ScheduleUpdate.
Memos may contain reference information and/or metadata for the schedule that could change depending on other changes to the schedule configuration as a result of the ScheduleHandle.update call. In order to keep the memo consistent with the updated configuration, the ability to update the memo is necessary as well.

Describe the solution you'd like
Allow an updated memo object to be passed in the ScheduleHandle.update call in the ScheduleUpdate object.

Describe alternatives you've considered
There do not seem to be other ways to track metadata associated with a schedule apart from the memo field, so this seems to be the only solution.

Additional context
N/A

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Python SDK implementation of ScheduleHandle.update and the ScheduleUpdateInput/ScheduleUpdate definitions. Check how schedule memos are created and how update requests are tested. Done means an updated memo can be passed through ScheduleHandle.update and the relevant tests cover the new behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.