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

Publish OpenTelemetry schema for each spec version #1693

Closed
tigrannajaryan opened this issue May 12, 2021 · 1 comment · Fixed by #1858
Closed

Publish OpenTelemetry schema for each spec version #1693

tigrannajaryan opened this issue May 12, 2021 · 1 comment · Fixed by #1858
Assignees
Labels
area:semantic-conventions Related to semantic conventions spec:miscellaneous For issues that don't match any other spec label

Comments

@tigrannajaryan
Copy link
Member

According to OTEP 0152 we need to publish a schema file per version.

Here is the preliminary plan to do it:

Corresponding discussion in the website repo: open-telemetry/opentelemetry.io#577

@tigrannajaryan tigrannajaryan added the spec:miscellaneous For issues that don't match any other spec label label May 12, 2021
@tigrannajaryan tigrannajaryan self-assigned this May 12, 2021
@carlosalberto carlosalberto added the area:semantic-conventions Related to semantic conventions label May 25, 2021
@tigrannajaryan
Copy link
Member Author

Draft PR open for manually publishing the first version open-telemetry/opentelemetry.io#599

tigrannajaryan added a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Aug 10, 2021
The action should be triggered manually after every spec release
and will copy/update schema files from this repository to the
website repository so that they become available publicly.

The publish-schemas action after manual triggering will create a PR
in https://github.com/open-telemetry/opentelemetry.io repo, and the
PR needs to be approved and merged manually.

This is similar to how we publish doc updates from language repos
to the website repo.

Resolves open-telemetry/opentelemetry.io#577
Resolves open-telemetry#1693
tigrannajaryan added a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Aug 10, 2021
The action should be triggered manually after every spec release
and will copy/update schema files from this repository to the
website repository so that they become available publicly.

The publish-schemas action after manual triggering will create a PR
in https://github.com/open-telemetry/opentelemetry.io repo, and the
PR needs to be approved and merged manually.

This is similar to how we publish doc updates from language repos
to the website repo.

Resolves open-telemetry/opentelemetry.io#577
Resolves open-telemetry#1693
tigrannajaryan added a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Aug 10, 2021
The action should be triggered manually after every spec release
and will copy/update schema files from this repository to the
website repository so that they become available publicly.

The publish-schemas action after manual triggering will create a PR
in https://github.com/open-telemetry/opentelemetry.io repo, and the
PR needs to be approved and merged manually.

This is similar to how we publish doc updates from language repos
to the website repo.

Resolves open-telemetry/opentelemetry.io#577
Resolves open-telemetry#1693
SergeyKanzhelev added a commit that referenced this issue Aug 30, 2021
* Add automated Schema File publish action

The action should be triggered manually after every spec release
and will copy/update schema files from this repository to the
website repository so that they become available publicly.

The publish-schemas action after manual triggering will create a PR
in https://github.com/open-telemetry/opentelemetry.io repo, and the
PR needs to be approved and merged manually.

This is similar to how we publish doc updates from language repos
to the website repo.

Resolves open-telemetry/opentelemetry.io#577
Resolves #1693

* Make branch name and commit message more relevant

Co-authored-by: Sergey Kanzhelev <[email protected]>
joaopgrassi pushed a commit to dynatrace-oss-contrib/semantic-conventions that referenced this issue Mar 21, 2024
* Add automated Schema File publish action

The action should be triggered manually after every spec release
and will copy/update schema files from this repository to the
website repository so that they become available publicly.

The publish-schemas action after manual triggering will create a PR
in https://github.com/open-telemetry/opentelemetry.io repo, and the
PR needs to be approved and merged manually.

This is similar to how we publish doc updates from language repos
to the website repo.

Resolves open-telemetry/opentelemetry.io#577
Resolves open-telemetry/opentelemetry-specification#1693

* Make branch name and commit message more relevant

Co-authored-by: Sergey Kanzhelev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:semantic-conventions Related to semantic conventions spec:miscellaneous For issues that don't match any other spec label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants