Skip to content

Remove default for --registry option with --v2 and/or --future #1279

@lmolkova

Description

@lmolkova

#1260 (comment)

weaver registry {command} defaults to semconv main branch when registry is not provided explicitly. It does not make sense:

  • only semconv need to run against semconv repo, other registries should use theirs
  • live-check should not run against semconv main branch, it could run against specific released version. It should be possible to run against latest released version or it may run against schema_url received in the telemetry.

So with some modifications it makes sense for live-check, but it can be added later. While we have unstable window with v2 I think we should stop supporting default registry all together and can bring it back for specific commands later

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions