Add content-type to support protobuf for runkperf #133
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.
This pull request introduces a new
content-type
flag to specify the content type (either JSON or Protocol Buffers) and updates the load profile generation to include this content type. The most important changes are summarized below:New Feature Addition:
contrib/cmd/runkperf/commands/bench/root.go
: Added a newcontent-type
flag to thecommonFlags
array to allow users to specify the content type as either JSON or Protocol Buffers. ([contrib/cmd/runkperf/commands/bench/root.goR83-R87](https://github.com/Azure/kperf/pull/133/files#diff-fbb70fa148e5f27e9fdf3e41d16d936d23670184a4e0bd5792fed70eb56fb036R83-R87)
)Load Profile Update:
contrib/cmd/runkperf/commands/bench/utils.go
: Updated thenewLoadProfileFromEmbed
function to set theContentType
field in the load profile specification based on the newcontent-type
flag. ([contrib/cmd/runkperf/commands/bench/utils.goL147-R147](https://github.com/Azure/kperf/pull/133/files#diff-0ecb63839ef4aa98fe23783072cffdf675738d1df358e0e5251cbe287b43e474L147-R147)
)