Skip to content

refactor(runtime): use the SDK host for A/B lifecycle #11

Description

@XnLemon

Problem

Runtime A and Runtime B duplicate HTTP serving, registration lease observation, cancellation, bounded shutdown, and deregistration. This makes the sample entrypoints long and allows lifecycle behavior to drift.

Proposal

After NeKiro-project/nekiro-sdk-go#3 is accepted, migrate both entrypoints to agent/host while retaining their runtime-owned configuration, Nacos TLS/mTLS transport, Router authentication, endpoint challenge, and Handler construction.

Acceptance criteria

  • Runtime A and B use the same host lifecycle implementation.
  • Direct registration-disabled mode remains explicit and supported.
  • Registration, serve, heartbeat, shutdown, and deregistration failures preserve staged errors.Is/As behavior.
  • Existing unit and E2E behavior remains unchanged.
  • The SDK dependency is pinned to one immutable revision.

Fallback delta: removed 0, retained 0, added 0, net +0
Added fallback evidence: none

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions