-
Notifications
You must be signed in to change notification settings - Fork 625
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
Handle boolean, integer and float values in Configuration #662
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! I do have a thought on accepting more than just capital T/F for bool, but that could be relaxed later on. Thanks!
@@ -77,6 +77,11 @@ | |||
"default_meter_provider" (this is not actually necessary since the | |||
OpenTelemetry API provided providers are the default ones used if no | |||
configuration is found in the environment variables). | |||
|
|||
Configuration values that are exactly ``"True"`` or ``"False"`` will be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typically lowercase "true" or "false" work here as well. Thoughts on accepting those?
Fixes #647