docs: propose datumctl compute developer experience#111
Conversation
Outlines the proposed `datumctl compute` command group — covering deploy, status, rollout, logs, instance inspection, and quota — with example output for each workflow. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
scotwells
force-pushed
the
docs/datumctl-compute-dx
branch
from
2cbe48b to
a775ae6
Compare
scotwells
requested review from
0xmc,
JoseSzycho,
aflor024,
bmertens-datum,
drewr,
ecv,
jacobsmith928,
kevwilliams,
mattdjenkinson,
mksinghtx,
privateip,
savme,
yahyafakhroji and
zsmithnyc
mattdjenkinson
left a comment
mattdjenkinson
left a comment
There was a problem hiding this comment.
This is great - would be good as a follow up to do similar with AI Edge?
|
@mattdjenkinson yes, something I'd like to play with is a plugin system for datumctl datum-cloud/datumctl#197. |
|
|
||
| All filters translate to label selectors against the platform's telemetry system. There is no per-city fan-out — the CLI queries a single endpoint and the label index handles scoping. | ||
|
|
||
| ### 5. Inspect and debug instances |
There was a problem hiding this comment.
do we want to support datumctl compute ssh or similar to get a shell into a running instance?
There was a problem hiding this comment.
Yes, that will be a long term goal. Though, I'd probably do datumctl compute exec to align with kubectl / docker.
There was a problem hiding this comment.
I'd also want to have a debug command that lets you attach ephemeral containers to instances so you can get additional tools that may not be installed on the running containers.
scotwells
changed the title
scotwells
force-pushed
the
docs/datumctl-compute-dx
branch
from
1e2baaa to
a775ae6
Compare
scotwells
changed the title
drewr
left a comment
drewr
left a comment
There was a problem hiding this comment.
Good stuff. Excited for it to be real.
5 participants
Summary
Proposes the developer experience for
datumctl compute— the CLI surface for deploying and managing containerized workloads on Datum Cloud.The RFC covers the command taxonomy, flag design, interactive flows, output formats, and example workflows for the three primary use cases: flag-driven deploy, manifest-driven deploy, and day-2 operations (scale, rollout, restart, status).
Related
Part of #98. Implementation tracked in #113.