Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feature: `mocactl bundles list` to enumerate caller's live config bundles

Open
  • Is something wrong?
#559 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, cli

Research direction

Start by reading the existing mocactl bundles delete command and the control plane API it calls, then look at how mocactl promote authenticates and returns bundle metadata. Add a caller-scoped list operation that reports the digest, size, promoted-at time, and server-tracked state in text and JSON output. Done means callers can list their live bundles and identify one to delete; the issue does not name files or tests.

Written by the indexing model from the issue text.

Description

enhancement
Feature Description

mocactl bundles today exposes only delete DIGEST, keyed by a digest the caller must already hold. There is no way to ask "what bundles do I currently own?"

That gap turns any crash between mocactl promote returning and whatever persists the digest client-side into an unrecoverable orphan. The bundle counts against the caller's budget until TTL, and the caller has no way to find it to mocactl bundles delete it.

Repro

# promote persists the bundle on the server *before* returning the digest to the client
mocactl promote /path/to/bundle --json
# → {"digest":"sha256:335201…","uploaded":true, ...}
#
# If the parent process dies between that response and whatever
# would have written the digest down (a note file, a ledger row,
# MOCA.md), the digest is lost but the bundle lives on the server.

Verified with a probe against the live cluster: promoted a bundle, "forgot" the digest, had to drop to redis-cli KEYS 'config:bundle:*' on the control plane to recover it before mocactl bundles delete could clean up. Cluster-admin surface — defeats the purpose

This is similar to #552

Proposed Solution

Add mocactl bundles list [--json] that calls the control plane scoped to the authenticated caller and prints digest, size, promoted-at, and whatever state the server tracks

Want to contribute?
  • I would like to work on this issue.
Additional Context

No response

Dominant language
TypeScript
Stars
4
Forks
9
Avg merge
9h 31m
Merged PRs (30d)
139

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rossoctl/moca

All issues in rossoctl/moca

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.