Skip to content

Conversation

migmartri
Copy link
Member

Propagate material annotations to subject structs. This will enable enhanced ingestion upstream.

In another patch, a similar feature #383 will be handled for our custom git head subject.

Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
@migmartri migmartri requested a review from danlishka October 23, 2023 21:47
"sha256": "580ac09da7771920dfd0c214964e7bfe4c27903bcbe075769a4044a67c9a390a"
}
},
"annotations": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[not blocking / just a consideration]
Is it expected to have a JSON key in plural which value is not an array? In this case, it's annotations, meaning that 1 annotation is <key, value> in that hash.

Copy link
Member Author

@migmartri migmartri Oct 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's part of the in-toto spec upstream.

In fact, it seems that a key-value pair is what makes indeed one annotation.

Copy link
Member

@danlishka danlishka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@migmartri migmartri merged commit 49ac85f into chainloop-dev:main Oct 29, 2023
@migmartri migmartri deleted the add-annotations-to-subject branch October 29, 2023 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants