Skip to content
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

Migrate semantic conventions code generation to weaver #3089

Closed
lmolkova opened this issue Oct 9, 2024 · 1 comment · Fixed by #3105
Closed

Migrate semantic conventions code generation to weaver #3089

lmolkova opened this issue Oct 9, 2024 · 1 comment · Fixed by #3105
Assignees
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@lmolkova
Copy link

lmolkova commented Oct 9, 2024

Semantic Convention tooling group is deprecating build-tools in favor of new code-generation tool - weaver, see open-telemetry/build-tools#322 for the details.

Build-tools are compatible with the latest version of semantic-convention (1.28.0), but might become incompatible with the future versions of semantic-conventions. New features (such as event definition) are added to the weaver only and won't be supported by the build-tools.

Migration steps are documented here along with some non-normative guidelines on the code organization and artifact stability.

Looking for volunteers and happy to help or provide any additional details.

@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 9, 2024
@marcalff
Copy link
Member

marcalff commented Oct 15, 2024

In progress, but blocked by:

@marcalff marcalff self-assigned this Oct 16, 2024
@marcalff marcalff added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants