dubbo-admin-discovery
Implements and reviews dubbo-admin registry discovery changes. Use when the user asks about Zookeeper or Nacos discovery, ListAndWatch, informers, discovery factories, discovery subscribers, ServiceProviderMetadata or ServiceConsumerMetadata processing, or Application, Service, RPCInstance, and Instance derivation under pkg/core/discovery/ and pkg/core/controller/. Do not use for engine-sourced RuntimeInstance behavior.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 4.1k
- Forks
- 2.2k
01 前言 Front Matter
- name
- dubbo-admin-discovery
- description
- Implements and reviews dubbo-admin registry discovery changes. Use when the user asks about Zookeeper or Nacos discovery, ListAndWatch, informers, discovery factories, discovery subscribers, ServiceProviderMetadata or ServiceConsumerMetadata processing, or Application, Service, RPCInstance, and Instance derivation under pkg/core/discovery/ and pkg/core/controller/. Do not use for engine-sourced RuntimeInstance behavior.
02 资源文件 2
- 参考文档evals/evals.json1.3 KB
- 参考文档references/discovery-flow.md10.2 KB
03 SKILL.md 正文
dubbo-admin Discovery
Purpose
Use this skill to trace registry-sourced resources from ListWatcher input through informer events, EventBus dispatch, subscribers, store writes, and derived mesh resources.
When to use
Use for Zookeeper or Nacos registry flow, discovery ListWatchers, discovery subscribers, metadata-derived services, application instance counts, and registry event bugs.
Do not use for Kubernetes runtime infrastructure engine flow; use dubbo-admin-engine for RuntimeInstance behavior.
Inputs
Required:
- Registry type, resource kind, subscriber, or discovery package path.
- The event or resource transition being changed or debugged.
Optional:
- Example registry metadata.
- Store query or index involved.
- Console API result affected by discovery data.
If missing, start at pkg/core/discovery/component.go and identify the subscriber for the resource kind.
Workflow
- Read
pkg/core/discovery/component.gofor dependencies, informer creation, subscriber registration, and start behavior. - Inspect
pkg/core/controller/listwatcher.goandpkg/core/controller/informer.go. - Follow registry-specific ListWatcher creation through
pkg/core/discovery/factory.go. - Read the relevant subscriber under
pkg/core/discovery/subscriber/. - Verify resource writes against store and index behavior.
- Read
references/discovery-flow.mdfor subscriber registration and event flow details.
Output format
Return the resource flow, affected subscriber, store/index interactions, changed files, and validation commands or residual test gaps.
Validation
- Confirm informer events emit the expected
cache.DeltaType. - Confirm subscriber
ResourceKind()matches the event resource kind. - Confirm derived resources use stable resource keys.
- Run targeted subscriber or controller tests; use
make testfor broad discovery changes.
Edge cases
- Nacos and Zookeeper register extra subscribers conditionally.
- Delete events may need old objects and must not assume
NewObj()exists. - If dispatch semantics are the problem, switch to
dubbo-admin-events.
References
- Read
references/discovery-flow.mdfor ListWatcher, informer, and subscriber details.
04 同仓库更多 Skills
dubbo-admin-store
Implements and reviews dubbo-admin resource storage and indexing changes. Use when the user asks about ResourceStore APIs, store routing, memory store behavior, index registration, IndexCondition, ListByIndexes, PageListByIndexes, ByMeshIndex, radix-tree prefix lookup, or pkg/core/store/, pkg/core/store/index/, and pkg/store/. Do not use for frontend, Console API, discovery, or engine tasks unless they require store or index changes.
dubbo-admin-runtime
Implements and reviews dubbo-admin runtime component changes. Use when the user asks about component abstraction, component composition, runtime bootstrap, dependency ordering, registration, lifecycle, startup, shutdown, runtime builder behavior, or pkg/core/runtime/ and pkg/core/bootstrap/. Do not use for discovery, engine, store, Console API, or frontend tasks unless component lifecycle or dependencies are affected.
dubbo-admin-frontend
Implements and reviews dubbo-admin Vue 3 frontend changes. Use when the user asks about ui-vue3, Vue views or components, frontend routing, route metadata, API clients, Pinia stores, SearchDomain, i18n, layout tabs, traffic rule form design, frontend tests, or Vite, ESLint, and Prettier configuration. Do not use for Go backend internals unless coordinating an API contract with the frontend.
dubbo-admin-events
Implements and reviews dubbo-admin EventBus dispatching. Use when the user asks about Event, Emitter, Subscriber, SubscriptionManager, EventBus component registration, Subscribe or Unsubscribe behavior, Send dispatch rules, subscriber ProcessEvent flow, resource-kind based routing, or event error handling under pkg/core/events/. Do not use for a domain subscriber unless the task changes the event bus contract or dispatch semantics.
dubbo-admin-engine
Implements and reviews dubbo-admin resource engine changes. Use when the user asks about runtime infrastructure discovery, engine factories, Kubernetes or mock engine ListWatchers, RuntimeInstance informers, RuntimeInstanceEventSubscriber, engine leader election, or merging RuntimeInstance data into Instance resources under pkg/core/engine/ and pkg/engine/. Do not use for registry discovery unless the task concerns engine-sourced RuntimeInstance resources.
dubbo-admin-domain
Routes dubbo-admin architecture questions to the right domain skill. Use for cross-module questions, end-to-end flows, subsystem boundaries, or deciding whether runtime, discovery, engine, events, store, Console API, or frontend guidance applies. Prefer a narrower dubbo-admin-* skill when the request clearly targets one subsystem.