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.

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

Move otelcol api into api/otelcol #462

Merged
merged 1 commit into from
Oct 22, 2021

Conversation

pavolloffay
Copy link
Member

Signed-off-by: Pavol Loffay p.loffay@gmail.com

This is a preparation for #455

The instrumentation feature will be managed in a separate CR. Therefore it makes sense to create a subpackage for each CR. E.g.:

api/otelcol/v1alpha1
api/inst/v1alpha1

Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
Copy link
Member

@jpkrohling jpkrohling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. You mentioned "inst" in the description: can we have a few proposals before settling on the short name? I think the package name can still be instrumentation, though. In my opinion, inst is closer to install than to instrumentation.

@jpkrohling jpkrohling merged commit a45ce3d into open-telemetry:main Oct 22, 2021
@pavolloffay
Copy link
Member Author

api/instrumentation/ sounds good to me. Another alternative is api/otelist which would align with otelcol and it as well matches the short name of the instrumentation feature. Let's discuss it on the instrumentation PR

shree007 pushed a commit to shree007/opentelemetry-operator that referenced this pull request Dec 12, 2021
Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
ItielOlenick pushed a commit to ItielOlenick/opentelemetry-operator that referenced this pull request May 1, 2024
Signed-off-by: Pavol Loffay <p.loffay@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants