Skip to content

Conversation

@shaileshpadave
Copy link
Contributor

@shaileshpadave shaileshpadave commented Jun 30, 2025

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • WHOSUSING.md
  • Other (please describe):

NOTE: Please remember to run ./gradlew spotlessApply to fix any format violations.

Changes in this PR

  • Introduced CB Enabled for Service Registry
  • As we will be adding SignalAPI to oss updated clients in conductor-client
  • Few tests updates
  • Instead of 3 diff exceptions - APIException, OrkesClientException there is only one exception ConductorClientException

Describe the new behavior from this PR, and why it's needed
Issue #

Alternatives considered

Describe alternative implementation you have considered

@shaileshpadave shaileshpadave force-pushed the CCOR-12562-Fixed branch 5 times, most recently from 30a7023 to b8ac8f8 Compare June 30, 2025 12:24
@shaileshpadave shaileshpadave changed the title Introduce isCBEnabled flag for Service Registry SignalAPI and Execute API refactoring + Introduced CB Enabled for Service Registry Jul 1, 2025
public class ProtoRegistryEntry {
private final String serviceName;
private final String filename;
private final byte[] data;
Copy link
Contributor

Choose a reason for hiding this comment

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

keeping this change ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes we need them to deserialize the output from response.

.build();
.body(req);

// Only add query parameters if they are not null - let server use defaults
Copy link
Contributor

Choose a reason for hiding this comment

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

aren't these ifs already handled in conductor-client module ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No This is specific to executeWorkflow API. /workflow/execute/{name}/{version}

@@ -0,0 +1,96 @@
/*
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it part of conductor or orkes API? I don't see these endpoints here https://github.com/conductor-oss/conductor/tree/main/rest/src/main/java/com/netflix/conductor/rest/controllers .
If it is part of orkes API it should go to orkes-client project, from my standpoint

* @param returnStrategy Strategy for what data to return
* @return SignalResponse with data based on the return strategy
*/
public SignalResponse signal(String workflowId, Task.Status status, Map<String, Object> output, ReturnStrategy returnStrategy) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see this and other endpoints in conductor repository. Shouldn't it go to orkes client?

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