Flatten stability attribute in metadata attributes

[dmathieu]

This follows open-telemetry/opentelemetry-collector#14424

[dmathieu]

For this to pass, the workflow that updates the collector to its latest commit needs to run.

[ChrsMark]

For this to pass, the workflow that updates the collector to its latest commit needs to run.

This seems to run on Fridays:

opentelemetry-collector-contrib/.github/workflows/update-otel.yaml

Line 5 in d7ffb8b

- cron: "27 8 * * 5" # Run at 08:27 UTC on Fridays.

I'd be fine running this earlier to apply the fix immediately.

/cc @open-telemetry/collector-contrib-approvers

[mx-psi]

Seems like the automation failed: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/21897915348/job/63218327139 :(

[dmathieu]

Urgh it's a chicken and egg thing. The action can't run because this PR isn't merged, and this PR can't be merged until that action rans.

[dmathieu]

And I can't run update-otel locally.

go: downloading github.com/DataDog/datadog-agent/comp/core/secrets/utils v0.76.0-rc.4
go: github.com/open-telemetry/opentelemetry-collector-contrib/cmd/otelcontribcol imports
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlqueryreceiver imports
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlqueryreceiver/internal imports
github.com/thda/tds: reading github.com/thda/tds/go.mod at revision v0.1.7: git ls-remote -q --end-of-options origin in /Users/dmathieu/code/pkg/mod/cache/vcs/6f48db50355a4a73f13ccbde907ca315a2ce0168bac09468bf640bf86ba169a9: exit status 128:
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
go: github.com/open-telemetry/opentelemetry-collector-contrib/cmd/otelcontribcol imports
github.com/open-telemetry/opentelemetry-collector-contrib/receiver/snowflakereceiver imports
github.com/snowflakedb/gosnowflake imports
github.com/99designs/keyring imports
github.com/99designs/go-keychain: github.com/99designs/go-keychain@v0.0.0-20191008050251-8e49817e8af4: invalid version: git ls-remote -q --end-of-options origin in /Users/dmathieu/code/pkg/mod/cache/vcs/b7360a9bf0962ccbbbdde33d9b2afaa858108332182b20c493311b5829f1fd28: exit status 128:
fatal: 'origin' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

make[1]: *** [genotelcontribcol] Error 1
make: *** [update-otel] Error 2

[ChrsMark]

It seems to be a chicken and egg problem indeed and we cannot really migrate nicely since the stability field/key changes from object to string.

I guess we will need to break main for a while one way or the other.

@mx-psi would that be acceptable? Have we done something similar in the past?

[ChrsMark]

I also wonder if we could just run the update-otel workflow from a branch that has these changes. i.e. merging dmathieu:flatten-mdata-stability to open-telemetry:stability-patch and run the workflow from the latter. Then we could merge open-telemetry:stability-patch to the branch of the created PR (the one that the workflow will create) so as to have both updates in one place before merging it to main.

[dmathieu]

Changed the base branch of this PR so we can run the workflow in a branch that is not main.

[ChrsMark]

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/21939749987

[mx-psi]

It seems to be a chicken and egg problem indeed and we cannot really migrate nicely since the stability field/key changes from object to string.

I guess we will need to break main for a while one way or the other.

@mx-psi would that be acceptable? Have we done something similar in the past?

Sorry, missed this yesterday, I think the alternative you came up with sounds great