AMQ Adapter with CleverBRAG integration - compatibility check #23
Open
opened 2025-04-28 15:03:51 +00:00 by stanislav.hejny
·
1 comment
No Branch/Tag Specified
develop
api_docs
feat/63-cleverswarm-unidirectional
feat/61-multi-user-support
feat-58-backpressure-reactive-streams
fix/bp-report
otel-demo
cleverbrag-integration-2
cleverbrag-integration
code-formatting
errors-as-json
config-documemntation
fix-version
feat/#1
fix_testing
feat/readme
feat#2
feat#64
No results found.
Labels
Clear labels
Blocked
Needs feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
Projects
Clear projects
No project
Sprint May 15th - 28th
Assignees
aleenaumair (Aleena Umair)
argocd
CoreRasurae (Luis Mendes)
drew (Drew Morris)
eugen.thaci (Eugen Thaci)
freemo (Jeffrey Phillips Freeman)
hurui200320 (Rui Hu)
justin.morris
khird (Kyle Hird)
mngrif (Michael Griffith)
org.clevermicro (System User)
org.cleverswarm (System User)
org.inf-cd
salcedo (Brian Salcedo)
stanislav.hejny (Stanislav Hejny)
Clear assignees
Notifications
Due Date
No due date set.
Blocks
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#23
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
in order to complete the CleverBRAG - CleverMicro onboarding and integration, the CleverBRAG specific code must be developed for python-based adapter, that connects the generic adapter logic with CleverBRAG own endpoints.
There will be new file, clever_brag.adapter.py that will be included into CleverBRAG source code, which will initialize and start AMQ Adapter thread and provide the FastAPI public endpoints discovery logic.
At this time, I have identified a need for minor change in CleverBRAG code needed for AMQ Adapter. In order to convert JWT token to valid
Userobject, the AMQAdapter code needs access to R2RAuthProvider instance that the FastAPI uses for the same purpose. However it seems that the Providers container is a temporary local variable, not exposed after the R2RApp is built.In order to expose the R2RAuthProvider instance to AMQ Adapter, can you please add
providers: R2RProvidersas another init parameter for R2RApp object:and than also pass in the providers as input in py/core/main/assembly/builder.py, line #296:
this new attribute will be used like this:
@stanislav.hejny @aleenaumair
This ticket does not have points assigned, therefore can not be MoSCoWed.
This ticket is lacking priority (which needs to be set to backlog) as well as a milestone.
I am also curious why this is a CleverMicro ticket, it should be a CleverBrag ticket no?
AMQ Adapter with CleverBRAG integrationto AMQ Adapter with CleverBRAG integration - compatibility check