unbridled-41 opened a new issue, #6008:
URL: https://github.com/apache/rocketmq-dashboard/issues/6008
### Studio Version
branch: `rocketmq-studio` @ `7e7aa344`
### Runtime Environment
Backend tests: `cd server && mvn -o -B -ntp test
-Dtest='RocketMQAdminClientImplTest'`.
### Describe the Bug
The create path applies defaults the request may omit (`perm RW`, the
resolved cluster, `type NORMAL`) but answers with the request object, so a
caller receives `perm: null`, `clusterId: null` and `type: null` for a topic
that the next read reports as RW, cluster-bound and NORMAL. The update path
already back-fills the persisted remark for exactly this reason but not the
permission, cluster or type.
### Steps to Reproduce
`POST /api/topics/create {"instanceId":"inst-1","name":"orders"}` then `GET
/api/topics?instanceId=inst-1`: the create response says `perm: null`, the read
says `RW`.
### What Did You Expect to See?
The stored topic, as the read returns it.
### What Did You See Instead?
The request echoed back, with the applied defaults invisible.
### Impact
Create-then-report flows state wrong facts, and the response cannot be used
as the post-create resource.
### Acceptance Criteria
The create (and update) response reports the persisted permission, cluster
and type, with a regression test.
**Corresponding PR:** #ISSUEPR#
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
