-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oversight in the SLAS v1 field invocationID
?
#260
Comments
cc @adityasaky |
I think it's preferable to fix this by directly using the proto. I know @marcelamelara was interested in getting this done too, unfortunately I've been a little swamped. @marcelamelara do you have any cycles to help out here? |
Agreed. |
+1 to switching to using the protobufs in this implementation. IIRC, the last time I looked at making this change happen, it wasn't quite as simple as replacing one struct for the other, but I'll have some cycles in the next week or two, so I can take a look. |
The aforementioned change is still not submitted so the proto version is effectively unusable. Can we merge the fix for this issue in the meantime? #328 |
Is this worth a patch-release? This is technically a bug fix but I can pin to the commit hash if necessary. |
I'll try and tag a release tomorrow. There are a couple pending updates etc we should probably merge as well, I'll check if someone has a few to take a pass at fixing some of the CI issues! |
Description of the bug:
In the SLSA v1 provenance, the json tag for the field invocation id should be
invocationId
instead ofinvocationID
per slsa v1 spec on the official website and the proto.But the tag in in-toto-golang is
invocationID
in-toto-golang/in_toto/slsa_provenance/v1/provenance.go
Line 144 in 5fd5c67
The text was updated successfully, but these errors were encountered: