clevermicro/user-management
14
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

Implement query user endpoint for RabbitMQ #35

Merged
hurui200320 merged 1 commits from feat/34 into develop 2025-07-31 04:56:48 +00:00
Conversation 2 Commits 1 Files Changed 47
+3645 -1312
hurui200320 commented 2025-07-25 08:05:37 +00:00
Member
Copy Link
Copy Source

This PR implemented ticket clevermicro/user-management#34 for the user-service-v1 endpoint, along with all the infrastructures required to support the endpoints.

The changes are:

  • switch build tool to gradle for easier access to the private artifacts of clevermicro (although later Brian change the artifacts to public)
  • set up clevermicro amqp client
  • switched to official keycloak admin client instead of implementing it with webflux
  • implement the message formats for the RPC protocol, for now they are exclusive to auth-service, but in the future we will reuse (might with some changes) them for all RPC calls inside clevermicro (need a server lib for handling the message parsing and convertion)
  • implement the user query endpoint
  • implement unit test so the overall coverage is above 85%
  • fixed all issues found during the testing phase with shared env

Currently the latest docker image has been deployed to the shared env, see https://docs.cleverthis.com/en/architecture/microservices/shared-env#multi-user-support

This PR implemented ticket clevermicro/user-management#34 for the user-service-v1 endpoint, along with all the infrastructures required to support the endpoints. The changes are: + switch build tool to gradle for easier access to the private artifacts of clevermicro (although later Brian change the artifacts to public) + set up clevermicro amqp client + switched to official keycloak admin client instead of implementing it with webflux + implement the message formats for the RPC protocol, for now they are exclusive to auth-service, but in the future we will reuse (might with some changes) them for all RPC calls inside clevermicro (need a server lib for handling the message parsing and convertion) + implement the user query endpoint + implement unit test so the overall coverage is above 85% + fixed all issues found during the testing phase with shared env Currently the latest docker image has been deployed to the shared env, see https://docs.cleverthis.com/en/architecture/microservices/shared-env#multi-user-support
hurui200320 self-assigned this 2025-07-25 08:05:37 +00:00
hurui200320 added 9 commits 2025-07-25 08:05:39 +00:00
build: switch build tool to maven and configured amq adapter library
CI for publishing docker image / build-and-publish (push) Has been cancelled
Details
Unit test coverage / gradle-test (push) Failing after 2m4s
Details
8ad2a7becf
build: update public artifacts cd6f671b16
refactor(keycloak): use official admin client instead of re-invent the wheel 300b73aa8f
feat(RabbitmqRPC): implement basic support for RabbitMQ RPC.
Unit test coverage / gradle-test (push) Failing after 3m38s
Details
CI for publishing docker image / build-and-publish (push) Successful in 4m2s
Details
16c040b51b
feat: implemented RabbitMQ RPC endpoint for query user info.
CI for publishing docker image / build-and-publish (push) Successful in 3m34s
Details
Unit test coverage / gradle-test (push) Failing after 6m31s
Details
ec7052ddee 
ISSUES RELATED: clevermicro/user-management#34
test: implement unit tests for RabbitMQ RPC endpoint
Unit test coverage / gradle-test (push) Failing after 3m7s
Details
CI for publishing docker image / build-and-publish (push) Successful in 3m43s
Details
d39455eaca
test: implement extra unit test to read 85% goal
Unit test coverage / gradle-test (push) Successful in 3m36s
Details
CI for publishing docker image / build-and-publish (push) Successful in 3m47s
Details
81b010ea66
feat: add OpenTelemetry log exporter to victoria logs.
Unit test coverage / gradle-test (push) Successful in 5m5s
Details
CI for publishing docker image / build-and-publish (push) Successful in 6m23s
Details
ff0dcbda5e
fix: fix permission check rule resolving
Unit test coverage / gradle-test (push) Successful in 3m30s
Details
CI for publishing docker image / build-and-publish (push) Successful in 3m46s
Details
Unit test coverage / gradle-test (pull_request) Successful in 2m16s
Details
973a185f13 
This commit fix the way for resolving the permission check rule. Now it respect the request path

instead of randomly picking one.
hurui200320 requested review from stanislav.hejny 2025-07-25 08:05:50 +00:00
hurui200320 added a new dependency 2025-07-25 08:06:28 +00:00
#34 Implement RabbitMQ RPC endpoint for user management API
gitea-actions bot commented 2025-07-25 08:07:55 +00:00
Copy Link
Copy Source

Coverage is 85%

Coverage is 85%
hurui200320 added a new dependency 2025-07-25 08:12:36 +00:00
clevermicro/amq-adapter-java#40 - Implement user-service client
hurui200320 force-pushed feat/34 from 973a185f13 to bed3de76dd 2025-07-31 04:56:26 +00:00 Compare
hurui200320 merged commit bed3de76dd into develop 2025-07-31 04:56:48 +00:00
hurui200320 deleted branch feat/34 2025-07-31 04:56:50 +00:00
gitea-actions bot commented 2025-07-31 05:03:46 +00:00
Copy Link
Copy Source

Coverage is 85%

Coverage is 85%
Sign in to join this conversation.
Reviewers
No Reviewers
stanislav.hejny
Labels
Clear labels
Blocked
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.
Needs feedback
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
Signed-off: Owner
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.
 Signed-off: Scrum Master
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.
 Signed-off: Tech Lead
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.
 Spike
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.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aleenaumair (Aleena Umair) argocd CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) hurui200320 (Rui Hu) justin.morris mngrif (Michael Griffith) org.clevermicro (System User) org.cleverswarm (System User) org.inf-cd salcedo (Brian Salcedo) stanislav.hejny (Stanislav Hejny)
No Assignees hurui200320
2 Participants
Notifications
Due Date
No due date set.
Blocks
#34 Implement RabbitMQ RPC endpoint for user management API
clevermicro/user-management
You do not have permission to read 1 dependency
Reference: clevermicro/user-management#35
Delete Branch "feat/34"

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?