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
Copy file name to clipboardExpand all lines: features/vsa.feature
+52Lines changed: 52 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -171,3 +171,55 @@ Feature: VSA generation and storage
171
171
When ec command is run with "validate image --image ${REGISTRY}/acceptance/vsa-existing-image@sha256:${REGISTRY_acceptance/vsa-existing-image:latest_DIGEST} --policy acceptance/vsa-existing-ec-policy --public-key ${vsa-existing_PUBLIC_KEY} --rekor-url ${REKOR} --vsa-expiration 24h --output json"
172
172
Then the exit status should be 0
173
173
Then the output should match the snapshot
174
+
175
+
Scenario: VSA generation without upload backends shows warning
176
+
Given a key pair named "vsa-no-upload"
177
+
Given an image named "acceptance/vsa-no-upload-image"
178
+
Given a valid image signature of "acceptance/vsa-no-upload-image" image signed by the "vsa-no-upload" key
179
+
Given a valid Rekor entry for image signature of "acceptance/vsa-no-upload-image"
180
+
Given a valid attestation of "acceptance/vsa-no-upload-image" signed by the "vsa-no-upload" key
181
+
Given a valid Rekor entry for attestation of "acceptance/vsa-no-upload-image"
182
+
Given a git repository named "vsa-no-upload-policy" with
183
+
| main.rego | examples/happy_day.rego |
184
+
Given policy configuration named "vsa-no-upload-ec-policy" with specification
0 commit comments