You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: put CLI version and location under test explicit in sigstore-e2e + fix cgw - #103
What: Resolve the content gateway's CDN redirect before extracting the archive, drop the hardcoded fallback to RHTAS 1.4.2 and tufcli's private go install fallback, and make CLI_CGW_VERSION the single explicit, defaulted (pkg/api/values.go), overridable source of the version under test instead of inferring it from the cluster. Also adds CLI_LOCAL_DIR to pin the local strategy to an exact directory, and fixes the rekor-cli test to accept either entry type.
Why: A content gateway file URL redirects to an HTML page instead of the archive, so the download always failed and silently fell back to 1.4.2 — every CLI was validated against the wrong release while CI stayed green (confirmed via cosign reporting the 1.4.2 build on a 1.5.0 cluster). tufcli's fallback to go install had the same problem: it built an unrelated, outdated tag instead of the published artifact.
• Resolve content-gateway redirects before extracting archives and require an explicit OpenShift CLI
release version.
• Remove silent release and tufcli source-build fallbacks so missing published artifacts fail the
suite.
• Pin CI to GA 1.5.0, accept newer Rekor entries, and add download regression tests.
The following are alternative approaches to this PR:
1. Use the CGW strategy for published CLI tests
➕ Avoids rewriting versions in cluster-provided links.
➖ Would not exercise the operator’s ConsoleCLIDownload links or their platform-specific CLI selection.
Recommendation: Keep the OpenShift strategy’s explicit version pin and gateway redirect resolution. It tests the cluster-provided links while ensuring the downloaded binaries belong to a known published release; switching to CGW alone would lose that coverage.
openshift.goPin OpenShift CLI downloads and eliminate release fallback+38/-29
Pin OpenShift CLI downloads and eliminate release fallback
• Requires CLI_CGW_VERSION, applies it to content-gateway ConsoleCLIDownload links, and resolves their CDN redirects before extraction. Removes the hardcoded 1.4.2 retry while leaving non-gateway links on their existing download paths.
interstitial_test.goExercise versioned gateway redirects and hard failures+178/-0
Exercise versioned gateway redirects and hard failures
• Adds a version-aware gateway stub and tests interstitial resolution, use of the requested version, rejection of unpublished versions, and the missing-version error.
README.mdDocument which CLI build each strategy tests+29/-1
Document which CLI build each strategy tests
• Documents the required OpenShift version pin, lack of fallback, and the distinction between published CLI binaries and the unreleased operator used by E2E.
View medium (2) 1. Source-build guidance leads to a panic 🐞 Bug
Description
NewTufcli now directs source builds through PreferredSetupStrategy and tells users to set only
CLI_STRATEGY=goinstall, removing the private fallback's hardcoded tufcli module. When
GOINSTALL_MODULE is unset, selecting that strategy panics during strategy initialization rather
than building tufcli.
Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
The new tufcli source-build instruction omits a setting required by the selected strategy.
## Fix Focus Areas
- pkg/clients/tufcli.go[7-16]
- pkg/strategy/goinstall/goinstall.go[16-26]
## Recommended Fix
State that source builds also require `GOINSTALL_MODULE=github.com/securesign/tufcli`, or provide that module when tufcli selects the go-install strategy.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
IsContentGatewayLink classifies URLs by a path substring without checking the host, so
downloadArchive sends any matching archive URL to ResolveCDNLink. If a directly served archive
has /content-gateway/ in its path, its normal 200 response is rejected as a missing redirect
before extraction begins.
Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution
## Issue description
A path substring alone treats directly served archives on other hosts as gateway interstitials.
## Fix Focus Areas
- pkg/support/testSupport.go[153-167]
- pkg/strategy/openshift/openshift.go[57-66]
## Recommended Fix
Restrict gateway classification to the intended gateway hosts and path, while retaining a testable way to exercise the interstitial flow. Add a direct-archive test with a gateway-shaped path.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
kdacosta0
changed the title
fix: download the release under test from the content gateway
fix: put CLI version and location under test explicit in sigstore-e2e + fix cgw
Nov 4, 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
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: Resolve the content gateway's CDN redirect before extracting the archive, drop the hardcoded fallback to RHTAS 1.4.2 and tufcli's private
go installfallback, and makeCLI_CGW_VERSIONthe single explicit, defaulted (pkg/api/values.go), overridable source of the version under test instead of inferring it from the cluster. Also addsCLI_LOCAL_DIRto pin thelocalstrategy to an exact directory, and fixes the rekor-cli test to accept either entry type.Why: A content gateway file URL redirects to an HTML page instead of the archive, so the download always failed and silently fell back to 1.4.2 — every CLI was validated against the wrong release while CI stayed green (confirmed via
cosignreporting the 1.4.2 build on a 1.5.0 cluster). tufcli's fallback togo installhad the same problem: it built an unrelated, outdated tag instead of the published artifact.🤖 Generated with Claude Code
SECURESIGN-6181