Ability to change environment at Runtime

[TheXRMonk]

Feature description

Many release workflows with unity follows a promotion workflow, where the build binary is promoted through different environments. Right now there's no way to "wait" with initializing the datadog client (from DatadogInitialization in DatadogAndroidPlatform.cs), until we have acquired the environment from our launch flow. And even when we get the environment, there's no way to change the settings/options that the Datadog client runs under after it has been initialized.

Proposed solution

For changing environment at runtime: It would be beneficial to have an "invalid" environment and stack up messages (like the SDK does when the user's Permission is pending), and then send once permission has been granted and environment has been set.

Other relevant information

This was already discussed here;
#103 (comment)

[TheXRMonk]

Additionally, we would have the same issue with regions - we need to send data to a specific region due to regulations. Having this as a hardcoded field that we cant change at runtime almost makes this product unusable for us.

[fuzzybinary]

Late initialization is definitely on our radar as something that's needed. We're looking into it, but we don't have a firm timeline on what it will be available yet.

[TheXRMonk]

So does this mean that other customers are rebuilding binaries for different regions? Or is there a loophole we haven't found?

[fuzzybinary]

The one customer I know of that is doing late initialization has forked the SDK and performs the native initialization late through a call in C#, as they're willing to accept loss of data from start to their initialize call.

We're looking for a more robust long term solution that will prevent such data loss but still allow late configuration.

[TheXRMonk]

Thanks. That's also our immediate approach👍