-
Notifications
You must be signed in to change notification settings - Fork 893
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
Labels
area:semantic-conventions
Related to semantic conventions
spec:miscellaneous
For issues that don't match any other spec label
Comments
tigrannajaryan
added
the
spec:miscellaneous
For issues that don't match any other spec label
label
May 12, 2021
carlosalberto
added
the
area:semantic-conventions
Related to semantic conventions
label
May 25, 2021
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
According to OTEP 0152 we need to publish a schema file per version.
Here is the preliminary plan to do it:
/schemas
, so/schemas/1.4.0
will be a YAML file containing the schema for specification version 1.4.0./static/schemas/
./schemas
directory. This is a pre-requisite for spec release (and we can automate verification of this pre-requisite in the future)./schemas
and pushes it to https://github.com/open-telemetry/opentelemetry.io repo as a new PR (similar to what we already have for Java).https://opentelemetry.io/schemas/<version>
(deployed via Netlify).Corresponding discussion in the website repo: open-telemetry/opentelemetry.io#577
The text was updated successfully, but these errors were encountered: