Skip to content

Conversation

dimaqq
Copy link
Contributor

@dimaqq dimaqq commented Aug 29, 2025

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?

@dimaqq dimaqq changed the title chore: Friday item, rewrite vendored charm lib in pure Python chore: rewrite vendored tracing charm lib in pure Python Aug 29, 2025
)

for event in (
self.charm.on.start,
Copy link
Contributor Author

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,
Copy link
Contributor Author

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"]'
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Must check leadership first.

@dimaqq
Copy link
Contributor Author

dimaqq commented Sep 8, 2025

Based on a chat with Ben, I will reach out to the maintainers of tracing and certificate_transfer libraries with an offer that I would re-code those specific libraries in pure Python (ie drop Pydantic).

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.

rewrite the vendored tracing lib in pure Python

1 participant