-
Notifications
You must be signed in to change notification settings - Fork 70
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
Parse the agent configuration based on the MIME type when fetching it via HTTP #268
Comments
Hey! I'm interested in working upon it. Can you point me to the part of code where you're handling this? |
Hi @layzbot it's nice to hear that you are interested in working on this issue. Currently, this is handled is in the |
It should be handled in |
…arsing of raw properties
…. Remove redundant code
…ob in agent_test.yml
…en fetching it via HTTP (#1251) Co-authored-by: Marius Oehler <[email protected]>
In the current state, the agent is able to fetch a configuration from a HTTP endpoint using its
HttpPropertySource
.When a configuration is fetched, the agent considers it as a JSON. If the parsing fails - because it is not a JSON response - it will try to parse it using the YAML representation.
This behaviour should be optimized. The agent should immediately use the correct representation type (e.g. YAML) if a MIME type is provided in the response in order to prevent unnecessary Exception handling.
The text was updated successfully, but these errors were encountered: