allow overriding junit intake url with env#439
allow overriding junit intake url with env#439emilgelman wants to merge 1 commit intoDataDog:masterfrom
Conversation
| - `DD_TAGS`: set global tags applied to all spans. The format must be `key1:value1,key2:value2`. | ||
| - The resulting dictionary will be merged with whatever is in the `--tags` parameter. If a `key` appears both in `--tags` and `DD_TAGS`, whatever value is in `DD_TAGS` will take precedence. | ||
| - `DATADOG_SITE`: choose your Datadog site, e.g. datadoghq.com or datadoghq.eu. | ||
| - `DATADOG_JUNIT_INTAKE_URL`: override the full URL for the intake endpoint. |
There was a problem hiding this comment.
is this something we want to show to users? Are we doing it for sourcemaps?
There was a problem hiding this comment.
it seems more like an internal thing
There was a problem hiding this comment.
FYI in the sourcemaps readme we do have it mentioned here:
It is also possible to override the full URL for the intake endpoint by defining the DATADOG_SOURCEMAP_INTAKE_URL environment variable.
There was a problem hiding this comment.
oh sry I missed that. In any case, is there any reason to show it to users?
There was a problem hiding this comment.
I guess the only reason would be for the proxy case so customers can easily know what to configure.
juan-fernandez
left a comment
juan-fernandez
left a comment
There was a problem hiding this comment.
I'm going to block this PR until we figure out if HTTPS_PROXY can be used for this use case
|
@juan-fernandez any news about this? This is blocking our team from using this feature. |
I just answered directly on the issue thread: #438 |
4 participants
Allow setting a custom junit intake url with
DATADOG_JUNIT_INTAKE_URLenvironment variable