Closed shayancanonical closed 1 month ago
Hi @shayancanonical! We already have tracing v2
library that allows you to use it with both pydantic v1 and v2.
As we'll be dropping v1.tracing
soon you can bump to v2 and that should resolve your problem with tempo. See for instance this PR to see the changes that you need to do in charm code between v1 and v2.
In case you encounter any issues please let us know and feel free to reach out / open up an issue :)
Bug Description
We, in the data platform team, would like to relate to tempo-k8s to trace our charms. However, we already have various other charm libs (some from the observability team) that results in conflict with pydantic. For example, in mysql, some of these libs include:
pydantic < 2
pydantic>=1.10,<2
pydantic>=1.10,<2
However, the tempo_k8s/v1/tracing.py charm lib has a requirement of
pydantic>=2
. This is causing expected conflicts when installing requirementsTo Reproduce
charmcraft fetch-lib charms.tempo_k8s.v1.tracing
pydantic>=2
on line 29poetry lock --no-update
tox -e build-production
Errors in build
Environment
charmcraft version: 2.6.0 tox --version: 4.15.0 poetry --version: 1.8.3
Relevant log output
Additional context
One suggested way to resolve this would be to add support for
pydantic<2
in the tempo-k8s tracing charm lib