docs: state the CLI's real verbs on nats-account and nebula-ca - #4
Merged
Merged
Conversation
The entity table listed both as `ls / get`. Both specs in cmd/entity.go declare `ls, get, update, edit` -- the commands exist, they are just rejected for every tenant role by the update rule, which is a different statement from "the CLI does not offer them". The distinction matters to the reader the table is for: someone scripting against `stone` who sees `ls / get` concludes the command is absent and looks for another way in, when what they will actually get is a 404 from an authorization rule. The prose now says which it is, and keeps the part that was already right: neither entity can be created or deleted by hand, and signing keys go through the dedicated route. Found while writing the CLI's schema-drift tests (stone-age-io/stone-cli#4), which read the same spec table this page describes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The entity table in §4 listed both entities as
ls / get. Both specs incmd/entity.godeclarels, get, update, edit— the commands exist, they're just rejected for every tenant role by the update rule. That's a different statement from "the CLI doesn't offer them".The distinction matters for the reader this table is for: someone scripting against
stonewho seesls / getconcludes the command is absent and goes looking for another way in, when what they'd actually hit is a 404 from an authorization rule. The prose now says which it is, and keeps what was already correct — neither entity can be created or deleted by hand, and signing keys go throughPOST /api/org/nats-account/keys.Found while writing the CLI's schema-drift tests (stone-age-io/stone-cli#4), which read the same spec table this page describes.
🤖 Generated with Claude Code