baggage as CORRELATION_CONTEXT_HEADER instead of otcorrelations

[Asafb26]

Please answer these questions before submitting a bug report.

What version of OpenTelemetry are you using?

0.11

What version of Node are you using?

12

Please provide the code you used to setup the OpenTelemetry SDK

'use strict';

const opentelemetry = require("@opentelemetry/core")
const { NodeTracerProvider } = require("@opentelemetry/node")

const provider = new NodeTracerProvider({
    logLevel: opentelemetry.LogLevel.INFO
});

// Initialize the provider
provider.register();

Hello, I was planning to use open telemetry at my workspace but encounter an API issue between opentelemetry-ruby and opentelemetry-js - each of them uses a different header key to propagate the baggage items.

• js uses otcorrelations - while this key was the specified key in OT specs, nowadays it changed to baggage
• rb changed to baggage to sync with the latest specs.

Is there a way to override the CORRELATION_CONTEXT_HEADER key? or should I wait/open a PR for this?

[dyladan]

Thanks for the PR. That is the correct way to solve it.