Description
Component(s)
No response
Is your feature request related to a problem? Please describe.
In our "create component labels" script we have a few components that are just barely over GitHub's 50 character limit for labels. From a recent workflow run:
'extension/encoding/awscloudwatchmetricstreamsencoding' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/filesystemscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/memoryscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/networkscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/pagingscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/processesscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/processscraper' exceeds GitHubs 50-character limit on labels, skipping
'receiver/hostmetrics/internal/scraper/systemscraper' exceeds GitHubs 50-character limit on labels, skipping
Describe the solution you'd like
For each of these, there are suffixes in the last part of the path that can be removed since the suffix is already present in the path and therefore it's clear what type of component it is.
So extension/encoding/awscloudwatchmetricstreamsencoding
could become extension/encoding/awscloudwatchmetricstreams
and receiver/hostmetrics/internal/scraper/filesystemscraper
could become receiver/hostmetrics/internal/scraper/filesystem
.
This would get us under the 50-character limit for now and wouldn't require too many changes to how the script operates.
Describe alternatives you've considered
Support a field in mdatagen that allows us to manually shorten these, then generate the authoritative list of labels from mdatagen. The 50-character limit could be enforced during the generation step.
Additional context
No response