AMQ Adapter with CleverBRAG integration - compatibility check #23
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
2 participants
Notifications
Due date
No due date set.
Blocks
You do not have permission to read 1 dependency
Reference: clevermicro/amq-adapter-python#23
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
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
User
object, 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: R2RProviders
as 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