Implement ability to create RPC calls between two python services #18
Labels
No labels
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Support
Type
Task
Type
Testing
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#18
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.
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