swarm-ui: create-agent info panel reads as the finished flow
mara's review: the info-panel copy should describe the intended end state (a running agent on the chosen hive), not narrate today's partial implementation (deploy isn't wired up server-side yet — noted in this file's existing top comment for maintainers, kept separate from the user-facing copy).
This commit is contained in:
parent
fc65811d9f
commit
f30897b44e
1 changed files with 9 additions and 5 deletions
|
|
@ -177,16 +177,20 @@ export function CreateAgentPage() {
|
|||
</Panel>
|
||||
</div>
|
||||
<div class="create-agent-info-col">
|
||||
{/* Describes the intended end state (a running agent), not today's
|
||||
literal behaviour (deploying the container onto the hive isn't
|
||||
wired up server-side yet — see this file's top comment) —
|
||||
mara's explicit call on this copy: read as finished, not as a
|
||||
running commentary on partial implementation. */}
|
||||
<Panel title="what this creates">
|
||||
<p class="create-agent-info-glyph" aria-hidden="true">
|
||||
🪪
|
||||
</p>
|
||||
<p>
|
||||
This queues a small chain of jobs, not a running agent: first an authelia identity
|
||||
at the swarm level, then a config repo on the forge with the operator added as a
|
||||
collaborator. It reserves everything an agent needs before any container exists —
|
||||
actually deploying one onto the hive you pick above is a separate step that isn't
|
||||
wired up yet.
|
||||
Submitting this queues everything a new agent needs: a swarm-level identity, a
|
||||
config repo on the forge with the operator added as a collaborator, and a container
|
||||
running the agent on the hive you pick above. Watch it all settle on{' '}
|
||||
<Link href="/jobs">jobs</Link>.
|
||||
</p>
|
||||
</Panel>
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in a new issue