SP-45: Add asset-registry validate command#342
Open
Zgjim Haziri (ZgjimHaziri) wants to merge 1 commit intomainfrom
Open
SP-45: Add asset-registry validate command#342Zgjim Haziri (ZgjimHaziri) wants to merge 1 commit intomainfrom
Zgjim Haziri (ZgjimHaziri) wants to merge 1 commit intomainfrom
Conversation
Zgjim Haziri (ZgjimHaziri)
force-pushed
the
SP-45-add-asset-registry-validate-command
branch
from
2f8aaaf to
8378d01
Compare
Base automatically changed from
SP-39-add-asset-registry-proxy-commands
to
main
April 17, 2026 13:35
Three mutually exclusive modes: - --configuration/-c: validate a configuration JSON before import - --nodeKey: validate an already-stored node on the platform - -f: provide a full ValidateRequest file (multi-node/advanced) The CLI assembles the ValidateRequest envelope in the first two modes. Update SKILL.md, agentic guide, and command docs. Includes-AI-Code: true Made-with: Cursor
Zgjim Haziri (ZgjimHaziri)
force-pushed
the
SP-45-add-asset-registry-validate-command
branch
from
8378d01 to
a90cb3e
Compare
|
Kastriot Salihu (ksalihu)
approved these changes
Apr 17, 2026
Comment on lines
+112
to
+113
| - `--configuration <configuration>` – Inline JSON of the configuration to validate before import | ||
| - `-c, --configFile <configFile>` – Path to a JSON file containing the configuration to validate before import |
Collaborator
There was a problem hiding this comment.
the short hand looks very confusing considering we have both --configuration and --configFile. I would just remove it here and leave no short hand
|
|
||
| ``` | ||
| content-cli asset-registry validate --assetType BOARD_V2 \ | ||
| --packageKey my-pkg --configuration '{"components":[{"type":"kpi"}]}' |
Collaborator
There was a problem hiding this comment.
What was the reason for enabling configuration passing directly instead of using a file? I expect this to be very unusable even for an agent to do
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
3 participants
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.
Summary
Add
asset-registry validatecommand with three mutually exclusive modes for validating asset configurations:--configuration/-cwith--packageKey: validate a configuration JSON before import (CLI builds the ValidateRequest envelope)--nodeKeywith--packageKey: validate an already-stored node on the platform-f: provide a file with the full ValidateRequest body (standalone alternative to all other options)Proxies to Pacman's
POST /core/asset-registry/validate/{assetType}endpoint.Ticket: SP-45
Depends on: #341
Test plan
content-cli asset-registry validate --helpoutput verified