Allow configuration of custom junit intake URL

[emilgelman]

We have a proxy service that we use to upload Junit tests to Datadog, so we need a way to set a custom value for the junit intake URL - for example DATADOG_JUNIT_INTAKE_URL, similarly to DATADOG_SOURCEMAP_INTAKE_URL

[emilgelman]

#439

[lraucy]

Hello @emilgelman! Quick question to make sure we understand your use-case properly:

The CLI already supports the env var HTTPS_PROXY to configure a proxy (like HTTPS_PROXY=http://my-proxy-address:3128).

Would this configuration work for your use case, rather than introducing a new env var DATADOG_JUNIT_INTAKE_URL? If not, could you elaborate?

The DATADOG_SOURCEMAP_INTAKE_URL env var was mostly designed for internal testing, not for proxy usage.

[emilgelman]

hi @lraucy , apologies for the late response. I've tried using HTTPS_PROXY for this, yet I'm getting
[attempt 1] Retrying jUnitXML upload [report.xml]: Socket is closed

I'm getting the same error trying to use datadog-ci sourcemaps upload, yet it works when I override with DATADOG_SOURCEMAP_INTAKE_URL. Anything else I can try?

[lraucy]

Hi @emilgelman , sorry for the late response as well: what kind of proxy are you using? I have trouble to understand how datadog-ci sourcemaps upload could upload files to Datadog if you override DATADOG_SOURCEMAP_INTAKE_URL with your proxy URL: how does the proxy knows to which URL it should send sourcemaps to?

[emilgelman]

Hey @lraucy
I'll try to provide additional context. To enforce certain standards and perform custom audits, any request towards Datadog's API is being proxied by an internal service we have (we are using Spring Cloud Gateway).

For example, if we need to use the Monitors API, instead of calling GET api.datadoghq.com/api/v1/monitor, our users would call GET api.mycompany.com/v1/monitors, where certain business logic is executed and then the request is routed to Datadog's API as is, based on the endpoint.

Same goes for the datadog-ci utility, but here there is additional logic that knows to redirect calls to /v1/input and /api/v2/srcmap to https://sourcemap-intake.datadoghq.eu/api/v2/srcmap, since the target host is different from the "general" API.

For example, this is how we would execute datadog-ci:

export DATADOG_SOURCEMAP_INTAKE_URL="api.mycompany.com";
export DATADOG_API_KEY="<key...>";
datadog-ci sourcemaps upload "static/" --service=...

I hope I made it more clear now.

[ransoor2]

Hi DD
We are interested in this feature as well.
Is there any update?