-
Notifications
You must be signed in to change notification settings - Fork 896
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
Move OTLP specification to github.com/open-telemetry/opentelemetry-proto #3454
Move OTLP specification to github.com/open-telemetry/opentelemetry-proto #3454
Conversation
This will fail until open-telemetry/opentelemetry-proto#458 is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, pending acceptance in proto repository.
Don't merge until open-telemetry/opentelemetry.io#2642 is resolved. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't merge until open-telemetry/opentelemetry.io#2642 is resolved.
FYI, since this PR isn't deleting any pages, there is no need to wait on open-telemetry/opentelemetry.io#2642.
If later you decide to delete the pages (though not the section), we can add aliases to the updated section page to avoid any 404s on the website.
I think we still need to wait for open-telemetry/opentelemetry.io#2642 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See inline comments for copyedits.
Also note the potential impact of the following proposal:
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@tigrannajaryan et al.: is anything holding up this PR? |
I was waiting for the completion of open-telemetry/opentelemetry.io#2642 to make sure we don't break anything by deleting the content here. |
If you rebase this branch, I can test the branch, but the simplest would be to just merge in the changes, and then I'll test from |
f84d94b
to
c717ebe
Compare
c717ebe
to
6a684b6
Compare
Maybe someone should remove the |
This is rebased and ready to merge. @chalin let me if you need to confirm anything on your end, otherwise I can merge. I assume merging this changes nothing on our live website at least not until the next release. |
@tigrannajaryan - I just tested this PR and it breaks the website in obvious ways (detailed below) that will be fixed once the OTLP spec is published on the website (eg., via open-telemetry/opentelemetry.io#2786), and the next version of this OTel spec gets published too. So from my perspective, this PR is good to go. 🚀 This breaks the OTel website:
|
This doesn't really break the website, right? There will be no immediate changes to https://opentelemetry.io/ if we merge this PR. All the files modified by this PR are just in this repo. The website itself hosts its own files. Do I misunderstand something? |
Apologies for the confusion. What I meant to say is that in a local build, this PR breaks the website build.
Correct, it won't break the production build because the OTel website is pinned at v1.21.0 of the spec. |
Resolves #3415
Depends on open-telemetry/opentelemetry-proto#458
Depends on open-telemetry/opentelemetry.io#2642