Skip to content

Releases: rossoctl/rossoctl-cli

v0.1.3-alpha.1

v0.1.3-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@esnible esnible released this 23 Jul 12:48
c038933

Renaming from kagenti to rossoctl

v0.1.2-alpha.1

v0.1.2-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@esnible esnible released this 20 Jul 21:05
81d6726
Add cortex file-backed backend, context types, and cortex commands (#15)

* Add cortex file-backed backend, context types, and cortex commands

Introduce a Context Type ("k8s"/"cortex") and a rossoctlclient.Rossoctl
interface implemented by both apiclient.Client (HTTP) and the new
cortexclient.FileClient (file-backed). rossoctlclient.NewClient dispatches
on the context type.

Add `cortex` commands (start/stop/status/doctor): start/stop/status
resolve or create a cortex-typed context, and doctor is an offline
environment preflight ported from rossoctlx. `cortex start` registers the
rossoctlx start flags. `config delete-context` is also added.

FileClient derives its config paths (honoring XDG_CONFIG_HOME /
ROSSOCORTEX_CONFIG_DIR), seeds its agents/state files, implements
ListAgents (from the agents.json "agents" map) and CreateAgent (records
agent metadata with a Created timestamp).

Move the config dir and binary install location from $HOME/.rossoctl to
$HOME/.config/rossoctl.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Ed Snible <snible@us.ibm.com>

v0.1.1-alpha.1

v0.1.1-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@esnible esnible released this 20 Jul 14:39
39e5341
Don't auto-create contexts on read; seed namespace on login (#14)

get-contexts, use-context, and the --context override now use a
read-only config load and never create or seed a context:

  - get-contexts on an empty config prints just the header
  - use-context errors on an unknown/empty config
  - --context fails if the named context does not exist

The current-context path still seeds a default-server context on first
use, so resource commands (agents/tools) work out of the box.

login now seeds a blank context namespace with the first namespace the
server reports (best-effort; existing namespaces are preserved).

When a context has no namespace, the error now directs the user to run
`rossoctl login` rather than `config set-context --namespace`.

Signed-off-by: Ed Snible <snible@us.ibm.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v0.1.0-alpha.1

v0.1.0-alpha.1 Pre-release
Pre-release

Choose a tag to compare

@esnible esnible released this 17 Jul 22:32
44932b1

Test release to confirm automation. Limited experimental functionality.