feat: add sf package trust link status command (W-23970571) - #1274
Open
sshyamala-sfdc wants to merge 2 commits into
Open
feat: add sf package trust link status command (W-23970571)#1274sshyamala-sfdc wants to merge 2 commits into
sshyamala-sfdc wants to merge 2 commits into
Conversation
Add the hidden/beta `sf package trust link status` command that reports the connected authoring org's Public Secure (VerifiedDev) trust-link state: Not Linked, or the link's status (Pending/Accepted/Declined/Revoked/Failed) with the timestamps that are set. Thin wrapper over PackageTrustLink.status. Pins @salesforce/packaging 5.0.9-spi.1 (the prerelease that adds status). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… t/packaging-distribution/w-23970571/trust-link-status # Conflicts: # command-snapshot.json # package.json # yarn.lock
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.
What & Why
Adds the
sf package trust link statuscommand (W-23970571, SPI / Public Secure), the developer/authoring-org side verb that reports where a Public Secure (VerifiedDev) trust link stands in the two-way handshake. Thin oclif wrapper overPackageTrustLink.status()in@salesforce/packaging.Behavior
Read-only. Runs against the connected authoring org (the 1GP namespace org or 2GP Dev Hub); standard
--target-org/--api-version/--json.{ Status: 'Not Linked', linked: false }.Pending/Accepted/Declined/Revoked/Failed) with the verified org, plus a line per timestamp that's set (Requested,Established,Revoked); returns the full result. Unset timestamps are omitted so--jsonstays clean.Hidden/beta command (
hidden = true; state = 'beta'), consistent with the siblingrequest/unlinkverbs; nopackage.jsonsubtopic entry.Files
src/commands/package/trust/link/status.ts— the command.messages/package_trust_link_status.md— summary/description/examples + output messages.test/commands/package/packageTrustLinkStatus.test.ts— 4 unit tests.schemas/package-trust-link-status.json,command-snapshot.json— new command entry.package.json/yarn.lock— pin@salesforce/packaging5.0.9-spi.1 (the prerelease addingstatus).Testing
Verified against the published
@salesforce/packaging@5.0.9-spi.1(not ayarn link):yarn buildclean, full unit suite 140 passing,snapshot:compareandschema:compareboth report no changes.Related
Library PR: forcedotcom/packaging#920 (adds
PackageTrustLink.status, publishes 5.0.9-spi.1). Sibling verbsrequestandunlinkalready onpackaging-distribution/spi.Merge order: merge the library PR #920 first (so the pinned prerelease is final), then this one.