remotecfg does not recognize --feature.community-components.enabled flag

[mikewyer]

What's wrong?

I have a customer who wants some metrics uploaded to their datadog instance.

When I put the otelcol.exporter.datadog block (and all the supporting blocks) in the alloy config directly, it works (after enabling the commandline flag).

When I put the same chunk of config in a remoteConfig, it fails with:

component evaluation failed: updating custom component: 171:2: the component "otelcol.exporter.datadog" is a community component. Use the --feature.community-components.enabled command-line flag to enable community components (and 1 more diagnostics)

even though the flag is enabled.

Steps to reproduce

1. Add the flag --feature.community-components.enabled=true to alloy's commandline.
2. Create a working otelcol.exporter.datadog config as part of the usual alloy configmap.
3. Add the same config to a GrafanaCloud pipeline to deploy as remoteConfig for this alloy instance.

System information

GKE

Software version

Alloy v1.9.1

Configuration

otelcol.exporter.datadog "customer" {
    client {
        timeout = "10s"
    }

    api {
        api_key             = remote.kubernetes.secret.datadog.data["apikey"]
        fail_on_invalid_key = true
    }

    metrics {
        delta_ttl = 1200
        endpoint  = "https://api.datadoghq.com"

        exporter {
            resource_attributes_as_tags = true
        }

        histograms {
            mode = "counters"
        }

        sums {
            initial_cumulative_monotonic_value = "keep"
        }

        summaries {
            mode = "noquantiles"
        }
    }
}

Logs

remotecfg does not seem to emit logs (which might be its own bug)

[dehaansa]

Should be fixed here: #3948 fix will be available in 1.10.0 (release candidate likely coming later this week)