-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider removing cmd/otecontribcol and cmd/otetestbedcol modules #27826
Comments
I would be ok with removing it, so long as the makefile targets continue to work, that's fine w/ me. We should consider doing the same in core |
The suggestion was accepted after discussing it in the Collector SIG meeting |
I'm in favor of removing it. I'd love to get @bogdandrutu's opinion on this, as I remember him being quite vocal about having that versioned. |
I would like to work on this. I will start with moving the tests out per the list. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
@atoulme if you are ok with it, I can work on this - Please and thank you. |
Sure thing! |
Go code in the
cmd/otecontribcol
andcmd/otetestbedcol
modules is auto-generated using the collector builder.cmd/otecontribcol
also has additional lifecycle tests for all the components that do not necessarily belong to that module.The go modules depend on all the other modules in the contrib repo. This makes the linter take up to 20 minutes just to build AST. The linter job often times out.
Do we really need to keep the generated code? Instead, we can generate the code whenever we need to build the
otecontribcol
orotetestbedcol
artifacts. The lifecycle tests can be moved to each component by autogenerating them with themdatagen
tool.Action items (assuming the suggestion is accepted):
cmd/otecontribcol
orcmd/otetestbedcol
#27850The text was updated successfully, but these errors were encountered: