Skip to content

SP-331: Document config nodes create/update/archive and permissions#351

Open
Zgjim Haziri (ZgjimHaziri) wants to merge 1 commit intomainfrom
SP-331-document-single-node-cli-commands
Open

SP-331: Document config nodes create/update/archive and permissions#351
Zgjim Haziri (ZgjimHaziri) wants to merge 1 commit intomainfrom
SP-331-document-single-node-cli-commands

Conversation

@ZgjimHaziri
Copy link
Copy Markdown
Contributor

Description

Adds user-guide documentation for the new single-node CLI commands — config nodes create, config nodes update, and config nodes archive — covering payload shape, validate-only mode, and force-archive semantics.

Also closes a long-standing gap by adding a top-level Permissions section to the config commands guide:

  • Studio packages and assets → require edit package permission.
  • OCDM packages and assets → require edit permission on the connected data pool.
  • Same rules apply to the new single-node commands.
  • Documents that config list silently filters out packages the caller has no access to (rather than failing).

Docs-only change.

Relevant links

Checklist

  • I have self-reviewed this PR
  • I have tested the change and proved that it works in different scenarios — N/A, docs-only
  • I have updated docs if needed

Made with Cursor

Add user-guide documentation for `config nodes create`, `config nodes
update`, and `config nodes archive`, and a top-level Permissions section
covering Studio (edit package) vs OCDM (edit data pool) requirements
and the `config list` permission filter behavior.

SP-331

Includes-AI-Code: true
Co-authored-by: Cursor <cursoragent@cursor.com>
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 8, 2026

@ZgjimHaziri Zgjim Haziri (ZgjimHaziri) requested a review from a team May 8, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant