Skip to content

Introduce api category into history APIs#9435

Open
yux0 wants to merge 6 commits intotemporalio:mainfrom
yux0:yx/exclude-health
Open

Introduce api category into history APIs#9435
yux0 wants to merge 6 commits intotemporalio:mainfrom
yux0:yx/exclude-health

Conversation

@yux0
Copy link
Contributor

@yux0 yux0 commented Mar 4, 2026

What changed?

Introduce api category into history APIs

Why?

There are some APIs we want to exclude from health check. Using API category is a more protective way to manage this group.

How did you test it?

  • built
  • run locally and tested manually
  • covered by existing tests
  • added new unit test(s)
  • added new functional test(s)

@yux0 yux0 requested review from a team as code owners March 4, 2026 03:01
@yux0 yux0 added the teams/cgs label Mar 4, 2026
Copy link
Member

@yycptt yycptt left a comment

Choose a reason for hiding this comment

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

Guess you'll have to add more for SAA like PollActivityExecution.

We may need to use proto custom options for this and define it along with the method... otherwise it's very easy to miss updating this code for new apis.

Copy link
Member

@bergundy bergundy left a comment

Choose a reason for hiding this comment

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

I would strongly recommend that you require that all server methods set a category and enforce it in genrpcwrappers and the chasm protoc plugin. It forces the dev to think about this while developing and prevents accidentally mis-categorizing APIs in the future.

@yux0 yux0 changed the title exclude ExecuteMultiOperation in health check Introduce api category into history APIs Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants