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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 4.1k
- Forks
- 2.2k
01 前言 Front Matter
- name
- dubbo-admin-engine
- description
- 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.
02 资源文件 2
- 参考文档evals/evals.json1.3 KB
- 参考文档references/runtime-engine-flow.md7.8 KB
03 SKILL.md 正文
dubbo-admin Engine
Purpose
Use this skill to trace runtime infrastructure data from engine ListWatchers through RuntimeInstance events into Instance resource lifecycle changes.
When to use
Use for engine component lifecycle, engine factory support, Kubernetes runtime instance watching, leader election for engine logic, and RuntimeInstance to Instance merge or delete behavior.
Do not use for registry metadata discovery; use dubbo-admin-discovery.
Inputs
Required:
- Engine type, RuntimeInstance behavior, or engine package path.
- Intended runtime to instance transition.
Optional:
- RuntimeInstance sample.
- Existing Instance resource state.
- Store indexes used to find related instances.
If missing, inspect pkg/core/engine/component.go and then the relevant factory under pkg/engine/.
Workflow
- Read
pkg/core/engine/component.gofor dependencies, config, informers, subscribers, and start behavior. - Check
pkg/core/engine/factory.gobefore adding or changing engine types. - Inspect implementation factories under
pkg/engine/. - Follow RuntimeInstance ListWatcher output into
pkg/core/controller/informer.go. - Read
pkg/core/engine/subscriber/runtime_instance.gobefore changing Instance merge or delete behavior. - Read
references/runtime-engine-flow.mdfor leader election and merge details.
Output format
Return the engine flow, affected RuntimeInstance transition, store/index interactions, changed files, and validation plan.
Validation
- Confirm engine depends on EventBus and ResourceStore.
- Confirm non-memory stores only run business logic under leader election.
- Confirm RuntimeInstance upsert and delete preserve RPC-sourced Instance state correctly.
- Use
make testfor changes touching informer events or Instance lifecycle.
Edge cases
- Runtime-only instances require enough identity fields.
- Runtime delete should update an Instance when RPC source remains, but delete it when no source remains.
- If the EventBus dispatch contract changes, switch to
dubbo-admin-events.
References
- Read
references/runtime-engine-flow.mdfor engine startup and RuntimeInstance handling.
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-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.
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.