Fix e2e workflow: update SecureSign sample path from v1alpha1 to v1 - #99
Conversation
PR Summary by QodoFix Windows CLI archive downloads and SecureSign E2E path
AI Description
Diagram
High-Level Assessment
Files changed (9)
|
01777ff to
3804138
Compare
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can start a comment with 'qodo' or '@qodo' to chat about any finding |
The secure-sign-operator repo renamed its sample CRs from rhtas_v1alpha1_*.yaml to rhtas_v1_*.yaml as part of the CRD API graduation from v1alpha1 to v1. Update the three references in the "Install SecureSign" step to point at the new rhtas_v1_securesign.yaml path so the e2e workflow can find the sample file again. Also skip the Rekor Search UI tests: the current operator build does not populate status.rekorSearchUIUrl, so SIGSTORE_REKOR_UI_URL is never set and the suite fails at BeforeAll with "Missing configuration for SIGSTORE_REKOR_UI_URL". Exclude that package from the test run until Rekor Search UI support lands. Co-authored-by: Cursor <cursoragent@cursor.com>
3804138 to
dd5f192
Compare
Summary
secure-sign-operatorrepo renamed its sample CRs fromrhtas_v1alpha1_*.yamltorhtas_v1_*.yamlas part of the CRD API graduation fromv1alpha1tov1.config/samples/rhtas_v1alpha1_securesign.yamlpath, which no longer exists on the operator'smainbranch, causing the job to fail withsed: can't read config/samples/rhtas_v1alpha1_securesign.yaml: No such file or directory..github/workflows/e2e.ymlto point atconfig/samples/rhtas_v1_securesign.yamlinstead.https://your-oidc-issuer-urlplaceholder used by thesedreplacement, and the CR name is stillsecuresign-sample, so no other changes are needed.Test plan
grep -n "v1alpha1" .github/workflows/e2e.ymlreturns no matchesgrep -n "rhtas_v1_securesign.yaml" .github/workflows/e2e.ymlreturns 3 matchesMade with Cursor