Add additional fields to support decoding the body

[thompson-tomo]

Is your feature request related to a problem? Please describe.

I want to be able to know the schema that was used to create the body content so that the body can be Deserialised

Describe the solution you'd like

The AgentConfigFile response message to be extended to include:

• bodyschema: a field to indicate to the schema used by the body
• bodycontentyype: how the body content was encoded

Describe alternatives you've considered

Only utilise a generic common schema

[michel-laterman]

There already is AgentContentFile.content_type, how is bodycontenttype different?

Also would bodyschema be specified? What is the use case?

[thompson-tomo]

Unfortunately I can't remember why I went and added bodycontenttype after initially raising this issue. In relation to bodyschema that is for knowing what schema deecribes the body and it would used for knowing if the schema was following the otel configuration spec etc

[tigrannajaryan]

Also would bodyschema be specified? What is the use case?

+1. @thompson-tomo can you please describe the use case?

[thompson-tomo]

@tigrannajaryan see my last reply,

In relation to bodyschema that is for knowing what schema deecribes the body and it would used for knowing if the schema was following the otel configuration spec etc

[tigrannajaryan]

In relation to bodyschema that is for knowing what schema deecribes the body and it would used for knowing if the schema was following the otel configuration spec etc

Who would be interested in knowing this? Is this for the agent to know or for the server to know? What exactly is the scenario where this comes into play? Let's say the agent receives an AgentContentFile. Is there a use case when the agent doesn't already know what's the schema of its own config file and needs to be told by the server?