-
Notifications
You must be signed in to change notification settings - Fork 1.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
[confmap] Support expansion for environment variables with time formats #11241
[confmap] Support expansion for environment variables with time formats #11241
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.
The changes make sense, the only thing I am unsure of is why the check existed.
You'll also need to create a change log entry for this as well with |
de250a6
to
d12a7b4
Compare
adec838
to
0b2af62
Compare
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.
I feel like adding the time.Time
case to the error check is the proper way to handle this. @mx-psi do you agree?
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11241 +/- ##
=======================================
Coverage 91.52% 91.52%
=======================================
Files 424 424
Lines 20222 20222
=======================================
Hits 18509 18509
Misses 1329 1329
Partials 384 384 ☔ View full report in Codecov by Sentry. |
Hey folks any chance this can get merged? 🙇🏻♀️ |
…ts (open-telemetry#11241) #### Description This addresses open-telemetry#10659. In open-telemetry#10800 we removed restrictions on the types that can be allowed if expanded but in our case, this still fails because of the checks existing in `provider.checkRawConfType()` This adds `time.Time` as a type in the `provider.checkRawConfType()` instead of removing it completely. #### Link to tracking issue Fixes open-telemetry#10659 <!--Describe what testing was performed and which tests were added.--> #### Testing - added a test case to handle time formats in provider.go and expand.go - added an e2e test case to handle time formats
…ts (open-telemetry#11241) #### Description This addresses open-telemetry#10659. In open-telemetry#10800 we removed restrictions on the types that can be allowed if expanded but in our case, this still fails because of the checks existing in `provider.checkRawConfType()` This adds `time.Time` as a type in the `provider.checkRawConfType()` instead of removing it completely. #### Link to tracking issue Fixes open-telemetry#10659 <!--Describe what testing was performed and which tests were added.--> #### Testing - added a test case to handle time formats in provider.go and expand.go - added an e2e test case to handle time formats
Description
This addresses #10659. In #10800 we removed restrictions on the types that can be allowed if expanded but in our case, this still fails because of the checks existing in
provider.checkRawConfType()
This adds
time.Time
as a type in theprovider.checkRawConfType()
instead of removing it completely.Link to tracking issue
Fixes #10659
Testing