Add mime_type field to InformationParameter in test_runs.proto - #1328
Merged
Conversation
Sayter99
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an optional
mime_typefield (tag 9) toInformationParameterinopenhtf/output/proto/test_runs.proto.Motivation
InformationParametercurrently only supports specifying the payload format via theInformationTagenum (or defaulting toBINARY). Addingmime_typeallows storing arbitrary MIME type strings for attachments/info parameters (matching the pattern inmfg_event.proto) so that downstream consumers and parsers can correctly identify the attachment format without losing the original MIME type.Changes
optional string mime_type = 9;tomessage InformationParameter.// next tag = 10.