Fix remote config applying with consecutive requests to the same resource

Signed-off-by: Bob Weinand <[email protected]>

Author: bwoebi

ext/sidecar.c

@@ -383,6 +383,11 @@ void ddtrace_sidecar_submit_root_span_data_direct(ddtrace_root_span_data *root,
     bool changed = true;
     if (DDTRACE_G(remote_config_state)) {
         changed = ddog_remote_configs_service_env_change(DDTRACE_G(remote_config_state), service_slice, env_slice, version_slice, &DDTRACE_G(active_global_tags));
+        if (!changed && root) {
+            // ddog_remote_configs_service_env_change() generally only processes configs if they changed. However, upon request initialization it may be identical to the previous request.
+            // However, at request shutdown some configs are unloaded. Explicitly forcing a processing step ensures these are re-loaded.
+            ddog_process_remote_configs(DDTRACE_G(remote_config_state));
+        }
     }
     if (changed || !root) {
         ddtrace_ffi_try("Failed sending remote config data", ddog_sidecar_set_remote_config_data(&ddtrace_sidecar, ddtrace_sidecar_instance_id, &DDTRACE_G(sidecar_queue_id), service_slice, env_slice, version_slice, &DDTRACE_G(active_global_tags)));