-
Notifications
You must be signed in to change notification settings - Fork 124
chore: rewrite vendored tracing charm lib in pure Python #2020
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
base: main
Are you sure you want to change the base?
Conversation
) | ||
|
||
for event in ( | ||
self.charm.on.start, |
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.
Re-check if start event is neeed, even with bundles.
|
||
for event in ( | ||
self.charm.on.start, | ||
self.charm.on.upgrade_charm, |
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.
Re-check if upgrade-charm is needed; are relation-related events triggered after charm upgrade, just like start and config-changed.
if not rel: | ||
return Destination(None, None) | ||
|
||
rel.data[self.charm.app]['receivers'] = '["otlp_http"]' |
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.
Must check leadership first.
Based on a chat with Ben, I will reach out to the maintainers of |
This is a Friday item PR.
It's one half of reimplementing vendored charm libs in pure Python.
This PR reimplements the (larger) tracing charm lib.
Not ready for review, but hopefully shows the direction I'm taking.
Fixes #2022
Open question: where to keep the equivalence tests when the vendored code is removed?