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

Schema URL constants do not resolve #2743

Closed
cbandy opened this issue Mar 27, 2022 · 1 comment · Fixed by #2744
Closed

Schema URL constants do not resolve #2743

cbandy opened this issue Mar 27, 2022 · 1 comment · Fixed by #2744
Labels
bug Something isn't working
Projects

Comments

@cbandy
Copy link
Contributor

cbandy commented Mar 27, 2022

Description

The specification is clear that schema files are available at https://opentelemetry.io/schemas/<version>:

The schema is [to] be available to be referred and downloaded at well known URL: https://opentelemetry.io/schemas/<version>

However, the URLs in the semconv packages cannot be downloaded. They end with v<version> rather than <version>.

const SchemaURL = "https://opentelemetry.io/schemas/v1.7.0"

$ curl -fS https://opentelemetry.io/schemas/v1.7.0
curl: (22) The requested URL returned error: 404 

$ curl -fS https://opentelemetry.io/schemas/1.7.0
file_format: 1.0.0
schema_url: https://opentelemetry.io/schemas/1.7.0
versions:
  1.7.0:
  1.6.1:
  1.5.0:
  1.4.0:

Environment

  • opentelemetry-go version: v1.6.0, though I see these constants have not changed for some time.

Other information

I looked for other projects that define OpenTelemetry schema URLs.

Perhaps something needs to change in https://github.com/open-telemetry/opentelemetry-go-build-tools ?

@cbandy cbandy added the bug Something isn't working label Mar 27, 2022
@cbandy cbandy changed the title Schema URLs constants do not resolve Schema URL constants do not resolve Mar 27, 2022
@tigrannajaryan
Copy link
Member

Thanks for catching this bug, @cbandy

@MrAlias MrAlias added this to the Release v1.6.1 milestone Mar 28, 2022
@MrAlias MrAlias added this to Needs triage in Bugs via automation Mar 28, 2022
@MrAlias MrAlias moved this from Needs triage to Low priority in Bugs Mar 28, 2022
Bugs automation moved this from Low priority to Closed Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Bugs
  
Closed
Development

Successfully merging a pull request may close this issue.

3 participants