123123213weqw opened a new issue, #1450:
URL: https://github.com/apache/rocketmq-dashboard/issues/1450
## Bug Report
### Runtime
- Branch: `rocketmq-studio`
- Base: `0ef5e2d`
- JDK: 21
### Problem
The Topic detail dialog offers **Rebuild on Broker** when a persisted Topic
has no route. `TopicPage.rebuildTopic()` calls both APIs without the selected
managed-instance ID:
```ts
await createTopic({ name, type, writeQueues, readQueues });
await getTopicRoutes(topic.name);
```
The backend now requires `instanceId` for Topic writes, so the rebuild
request is rejected with HTTP 400. Even if a write were accepted, the follow-up
route lookup would not be scoped to the instance whose Topic is being rebuilt.
Normal Topic creation already forwards `selectedInstanceId`; only the
rebuild path drops it.
### Reproduction
1. Select an Apache managed instance.
2. Open a Topic whose persisted record has no Broker route.
3. Click **Rebuild on Broker**.
4. Observe that `POST /api/topics/create` has no `instanceId` and fails
validation.
### Expected
Both the rebuild write and the route refresh use the Topic record's
`instanceId` (falling back to the current selected instance for legacy records).
### Scope
- forward the originating instance ID to `createTopic`
- forward the same ID to `getTopicRoutes`
- add a focused UI regression test
--
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]
