invocation.configSource.uri does not conform to SLSA schema #934
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
lcarva
added a commit
to lcarva/ec-cli
that referenced
this issue
Oct 4, 2023
Chains is not populating the `invocation.configSource.uri` attribute correctly, due to tektoncd/chains#934 This change relaxes the schema validation until the issue in Chains is fixed and widely adopted. Ref: RHTAPBUGS-857 Signed-off-by: Luiz Carvalho <[email protected]>
lcarva
added a commit
to lcarva/ec-cli
that referenced
this issue
Oct 4, 2023
Chains is not populating the `invocation.configSource.uri` attribute correctly, due to tektoncd/chains#934 This change relaxes the schema validation until the issue in Chains is fixed and widely adopted. Ref: RHTAPBUGS-857 Signed-off-by: Luiz Carvalho <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
According to its schema, the attribute
invocation.configSource.uriof a v0.2 SLSA Provenance is expected to be an URI, e.g. , e.g.:oci://quay.io/<org>/<repo>Actual Behavior
In 0.17.0, the
invocation.configSource.uriattribute does not conform to an URI schema, e.g.:quay.io/<org>/<repo>.This is similar to the issue fixed in #792.
The text was updated successfully, but these errors were encountered: