fix(cli): accept matching --name and metadata.name in contract commands#3282
Merged
Merged
Conversation
When both an explicit --name flag and metadata.name in the contract file were provided, the CLI rejected the command even if both values were identical. Accept the command when they match and, when they differ, emit an actionable error that tells the user how to resolve it. Also align the metadata.name of the example contracts with the names used in the SSDF, CRA and SLSA guides so the documented commands work as written. Fixes SOL-58 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Tomasz Knura <tomasz.knura@itsilesia.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
matiasinsaurralde
approved these changes
Jul 10, 2026
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
2 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.
When both an explicit
--nameflag andmetadata.namein the contract file were provided,workflow contract create/update/applyfailed withconflicting nameseven when the two values were identical. This broke documented, copy-paste invocations.This PR:
--nameandmetadata.nameare identical (the common, unambiguous case).--name "A" and metadata.name "B" differ: pass only one, or set them to the same value.ValidateAndExtractName.metadata.namein the SLSA/SSDF/CRA example contracts with the names used in the docs guides so the documented commands work as written (companion docs PR in platform-docs).closes https://linear.app/chainloop/issue/sol-58
🤖 Generated with Claude Code