chore: enhance CLI help: add example for signer spec and add some more explaining lines#1965
Conversation
On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
📝 WalkthroughWalkthroughThis PR updates CLI help text and documentation for component-version signing to add an example signer-spec section, clarify that credentials are resolved via Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com> Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
There was a problem hiding this comment.
🧹 Nitpick comments (1)
cli/docs/reference/ocm_sign_component-version.md (1)
94-94: Align wording with the new signer-spec scope.Line 94 says “override algorithm defaults”, but the surrounding text now consistently states signer-spec controls both algorithm and encoding. Consider updating this line to avoid mixed messaging.
Suggested wording tweak
-# Use a signer specification file to override algorithm defaults +# Use a signer specification file to override algorithm and encoding defaults🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@cli/docs/reference/ocm_sign_component-version.md` at line 94, Update the heading text "Use a signer specification file to override algorithm defaults" to reflect that signer-spec controls both algorithm and encoding (e.g., "Use a signer specification file to override algorithm and encoding defaults") so wording aligns with the rest of the document that describes signer-spec scope.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@cli/docs/reference/ocm_sign_component-version.md`:
- Line 94: Update the heading text "Use a signer specification file to override
algorithm defaults" to reflect that signer-spec controls both algorithm and
encoding (e.g., "Use a signer specification file to override algorithm and
encoding defaults") so wording aligns with the rest of the document that
describes signer-spec scope.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: d6f284b2-98c2-494b-9207-ae8b1fbfcdd1
📒 Files selected for processing (2)
cli/cmd/sign/component-version/cmd.gocli/docs/reference/ocm_sign_component-version.md
🚧 Files skipped from review as they are similar to previous changes (1)
- cli/cmd/sign/component-version/cmd.go
fabianburth
left a comment
There was a problem hiding this comment.
Approved for now, I agree we need this. Although we are striving away from our brief command lines helps (not just here, in a lot of commands).
On-behalf-of: Gerald Morrison (SAP) gerald.morrison@sap.com
What this PR does / why we need it
Enhance the help for the
ocm sign cvcommand and explain the signer spec and add an example config. Also explain signatureEncodingPolicy andPlainvs.PEM.Testing
How to test the changes
Commands that test the change:
-->
Verification
ocmSummary by CodeRabbit