Skip to content

Decide the naming convention of environment variable constants #454

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
Closed
TommyCpp opened this issue Feb 11, 2021 · 2 comments
Closed

Decide the naming convention of environment variable constants #454

TommyCpp opened this issue Feb 11, 2021 · 2 comments
Labels
A-common Area:common issues that not related to specific pillar release:required-for-stable Must be resolved before GA release, or nice to have before GA.
Milestone
Tracing SDK Stable

Comments

@TommyCpp
Copy link
Contributor

Follow up on the discussion from #451, we should decide the name convention of environment variable constants
@hdost hdost added this to the Tracing API And SDK Stable milestone Apr 12, 2023
@hdost hdost added A-common Area:common issues that not related to specific pillar release:required-for-stable Must be resolved before GA release, or nice to have before GA. labels Apr 12, 2023
@hdost
Copy link
Contributor

hdost commented Apr 12, 2023

This seems like a good candidate of things which should be consistent before we GA.

@cijothomas
Copy link
Member

I think we can close this, as we only use env. variables from otel spec, which are well defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-common Area:common issues that not related to specific pillar release:required-for-stable Must be resolved before GA release, or nice to have before GA.
Projects
None yet
Milestone
Tracing SDK Stable
Development

No branches or pull requests
3 participants
@hdost @cijothomas @TommyCpp