Tags field for event handler

[IgorChvyrov-sm]

Changes:

Added Orkes Event Clients for sync and async sdk clients
Added integration tests

[codecov]

Codecov Report

❌ Patch coverage is 81.60920% with 16 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/conductor/client/event/event_client.py	0.00%	10 Missing ⚠️
src/conductor/asyncio_client/event/event_client.py	66.66%	3 Missing ⚠️
...rc/conductor/asyncio_client/orkes/orkes_clients.py	66.66%	1 Missing ⚠️
src/conductor/client/orkes/orkes_event_client.py	96.42%	1 Missing ⚠️
src/conductor/client/orkes_clients.py	66.66%	1 Missing ⚠️

Files with missing lines	Coverage Δ
...ctor/asyncio_client/configuration/configuration.py	97.67% <ø> (ø)
...onductor/asyncio_client/orkes/orkes_base_client.py	100.00% <100.00%> (ø)
...nductor/asyncio_client/orkes/orkes_event_client.py	100.00% <100.00%> (ø)
src/conductor/client/orkes/orkes_base_client.py	100.00% <100.00%> (ø)
...rc/conductor/asyncio_client/orkes/orkes_clients.py	65.11% <66.66%> (ø)
src/conductor/client/orkes/orkes_event_client.py	96.42% <96.42%> (ø)
src/conductor/client/orkes_clients.py	70.83% <66.66%> (ø)
src/conductor/asyncio_client/event/event_client.py	86.95% <66.66%> (ø)
src/conductor/client/event/event_client.py	0.00% <0.00%> (ø)

... and 10 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nthmost-orkes]

I wanted a moment to look at the different API parameter orders, so I had Claude generate the following. Just wanted to put this somewhere since "developer intuition" (let's call it) is something we don't currently value in our API design and I wish we did.

If you wouldn't mind, @IgorChvyrov-sm could you add a few comments in the code just to acknowledge the asymmetry?

Thanks.

Technical Note: Sync vs Async API Signature Asymmetry

During review, we identified that the sync and async event tag APIs have different parameter orders due to different code generation tools:

Observed Behavior

• Sync API (src/conductor/client/codegen/api/event_resource_api.py):

  • put_tag_for_event_handler(self, body, name, **kwargs)
  • delete_tag_for_event_handler(self, body, name, **kwargs)
  • Body param comes before name param (swagger-codegen behavior)

• Async API (src/conductor/asyncio_client/http/api/event_resource_api.py):

  • put_tag_for_event_handler(self, name: StrictStr, tag: List[Tag], ...)
  • delete_tag_for_event_handler(self, name: StrictStr, tag: List[Tag], ...)
  • Name param comes before tag param (matches server signature)

Root Cause

Different code generators:

• Sync: swagger-codegen (older tool, puts body params before path params)
• Async: Likely openapi-generator (newer tool, preserves natural parameter order)

Implementation in This PR

This PR correctly adapts to both signatures:

• Sync calls use positional args: put_tag_for_event_handler(tags, name)
• Async calls use keyword args: put_tag_for_event_handler(name=name, tag=tags)

Both approaches are correct and will work as expected. Code comments have been added to help future maintainers understand this asymmetry.

Future Work

Consider regenerating the sync client with updated tooling to align parameter orders across sync/async APIs (tracked separately as technical debt).

Verified Against:

• Orkes server signature: EventResource.java:142 - putTagForEventHandler(String name, List<Tag> tags)
• Both Python implementations correctly map to PUT /event/{name}/tags with tags in request body

[nthmost-orkes]

See my longer reply above -- I just want to put comments into the spots where we're having to use different parameter orders for what should really be totally symmetrical API calls.

[IgorChvyrov-sm]

Hi, @nthmost-orkes.

I agree with your point about inconsistencies. Added a comment to highlight the inconsistency. Good catch, thank you!

[nthmost-orkes]

Great TY!