Implement ability to create RPC calls between two python services #18

Open
opened 2025-04-23 12:39:19 +00:00 by stanislav.hejny · 2 comments

Ref epic: CleverBRAG Onboarding #59

at this version the adapter works only in consumer mode (it registers its route information and is capable of receiving requests and responding to it).
task: The capability also to initiate (produce) a request and await for response still needs to be added. This will enable communication between two CleverThis services using AMQ delivery channel.
The feature will appear as a python function to the caller, that takes the usual (serializable) arguments, executes the corresponding function on the remote service and returns the return value back to the caller.

Main effort expected on this ticket is testing and integrating with the Service, verifying that the in/out parameters are (de)serialized correctly.

Ref epic: [CleverBRAG Onboarding #59](https://git.cleverthis.com/clevermicro/clevermicro/issues/59) at this version the adapter works only in consumer mode (it registers its route information and is capable of receiving requests and responding to it). task: The capability also to initiate (produce) a request and await for response still needs to be added. This will enable communication between two CleverThis services using AMQ delivery channel. The feature will appear as a python function to the caller, that takes the usual (serializable) arguments, executes the corresponding function on the remote service and returns the return value back to the caller. Main effort expected on this ticket is testing and integrating with the Service, verifying that the in/out parameters are (de)serialized correctly.
Owner

@stanislav.hejny @aleenaumair

This ticket is lacking priority (which needs to be set to backlog) as well as a milestone. I technically shouldnt MoSCoW but I will anyway. Please fix this before advancing the ticket in any way.

@stanislav.hejny @aleenaumair This ticket is lacking priority (which needs to be set to backlog) as well as a milestone. I technically shouldnt MoSCoW but I will anyway. Please fix this before advancing the ticket in any way.
aleenaumair added this to the V.01 milestone 2025-05-05 10:03:38 +00:00
Member

Hi,
Just want to reference a previous conversation around this, just for the sake of documenting it on the ticket's feedback; we discussed how setting Priority: Backlog overrides the Priority:High/ Med/ Low. So, until 'Backlog' gets moved to 'Status' label, we will be assigning high/med/low priority and keeping state 'unverified/verified' to depict tickets that are not 'In Progress' yet, meaning that they are still part of the backlog.
Please let us know as soon as the Backlog label is moved to the status queue, so that we can start adding that to the tickets. @freemo

In addition, the 'Type' label also needs editing, to differentiate type (task, epic and legendary) and category (bug, feature, config, documentation, support, discussion).
cc: @eugen.thaci

Hi, Just want to reference a previous conversation around this, just for the sake of documenting it on the ticket's feedback; we discussed how setting Priority: Backlog overrides the Priority:High/ Med/ Low. So, until 'Backlog' gets moved to 'Status' label, we will be assigning high/med/low priority and keeping state 'unverified/verified' to depict tickets that are not 'In Progress' yet, meaning that they are still part of the backlog. Please let us know as soon as the Backlog label is moved to the status queue, so that we can start adding that to the tickets. @freemo In addition, the 'Type' label also needs editing, to differentiate type (task, epic and legendary) and category (bug, feature, config, documentation, support, discussion). cc: @eugen.thaci
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#18
No description provided.