This is to resolve recent issues, and improve changes from a recent contribution in #20.
It provides a way for DD_AGENT_HOST and DD_TRACE_AGENT_URL to set the address the agent uses to communicate with the agent. This is helpful in containerized environments or when there's a provisioning layer used in the deployment of kong.
The reference format {vault://env/dd-agent-host} is transformed to mean DD_AGENT_HOST.
Local E2E testing has been performed on this to confirm the expected outcome.
Eg:
DD_AGENT_HOST=dd-agent DD_TRACE_AGENT_URL=http://datadog-agent:8126 kong start will send traffic to datadog-agent:8126 (url has priority over host).
This is to resolve recent issues, and improve changes from a recent contribution in #20.
It provides a way for DD_AGENT_HOST and DD_TRACE_AGENT_URL to set the address the agent uses to communicate with the agent. This is helpful in containerized environments or when there's a provisioning layer used in the deployment of kong.
The reference format
{vault://env/dd-agent-host}
is transformed to meanDD_AGENT_HOST
.Local E2E testing has been performed on this to confirm the expected outcome. Eg:
DD_AGENT_HOST=dd-agent DD_TRACE_AGENT_URL=http://datadog-agent:8126 kong start
will send traffic todatadog-agent:8126
(url has priority over host).Related issue #19