Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The components command should output providers #11570

Closed
andrzej-stencel opened this issue Oct 30, 2024 · 2 comments
Closed

The components command should output providers #11570

andrzej-stencel opened this issue Oct 30, 2024 · 2 comments
Assignees
@ChrsMark

Comments

@andrzej-stencel
Copy link
Member

Now that the Builder allows to specify providers in its config, I would expect the providers to be listed in the output of the otelcol components command beside connectors, exporters, extensions, processors and receivers.

Describe alternatives you've considered

I don't know of any way to find what providers my build uses other than trying them out with otelcol validate --config=provider:value, which is cumbersome.
@ChrsMark
Copy link
Member

ChrsMark commented Dec 4, 2024

I would like to try my hand at it. Can I get assigned?

@ChrsMark ChrsMark mentioned this issue Dec 16, 2024
Merged
github-merge-queue bot pushed a commit that referenced this issue Jan 22, 2025
@ChrsMark
Add support for providers in components command (#11900)
e2d8b6b 
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
This PR adds support for printing config providers with the `components`
command.

<!-- Issue number if applicable -->
#### Link to tracking issue

Related to
#11570

<!--Describe what testing was performed and which tests were added.-->
#### Testing

<!--Describe the documentation added.-->
#### Documentation

<!--Please delete paragraphs that you did not use before submitting.-->

---------

Signed-off-by: ChrsMark <[email protected]>
@ChrsMark
Copy link
Member

Now that #11900 is merged I think we can close this issue. (I don't remember why I didn't link them originally)

@andrzej-stencel @mx-psi @dmathieu feel free to close it if you agree.

@mx-psi mx-psi closed this as completed Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChrsMark ChrsMark

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mx-psi @ChrsMark @andrzej-stencel