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

Define OpAMP Protobuf schema stability guarantees #141

Merged

Conversation

tigrannajaryan
Copy link
Member

@tigrannajaryan tigrannajaryan commented Jan 5, 2023

The guarantees mostly mirror the guarantees for OTLP (open-telemetry/opentelemetry-proto#432), the primary difference being that OpAMP has no gRPC services defined and does not need any guarantees for service definitions.

This PR reflects the OpAMP Workgroup's discussions.

Resolves #134

@tigrannajaryan
Copy link
Member Author

@andykellr I am opening this draft so that we can discuss what else is necessary to resolve #134

@andykellr
Copy link
Contributor

I think this looks good.

The guarantees mostly mirror the proposal for OTLP
(open-telemetry/opentelemetry-proto#432), the primary
difference being that OpAMP has no gRPC services defined and does not need
any guarantees for service definitions.

Resolves open-telemetry#134
@tigrannajaryan tigrannajaryan force-pushed the feature/tigran/stability branch from 198a252 to 89b786f Compare May 15, 2023 16:06
@tigrannajaryan tigrannajaryan changed the title [DO NOT MERGE] Define OpAMP Protobuf schema stability guarantees Define OpAMP Protobuf schema stability guarantees May 15, 2023
@tigrannajaryan
Copy link
Member Author

OTLP Stability guarantees were merged: open-telemetry/opentelemetry-proto#432

This PR is ready for review and merging.

- No existing symbol will be deleted.

Future versions of the OpAMP specification may be extended by modifying the
Protobuf schema defined in this specification version. The following Protobuf schema
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we specify how deprecations will be handled for the spec?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't put anything thought into the subject of deprecations. I also don't see anything in OTLP spec to use as an inspiration. It is probably worth thinking about, but probably should be a separate PR.

@tigrannajaryan tigrannajaryan requested a review from PeterF778 May 16, 2023 14:35
@tigrannajaryan
Copy link
Member Author

@andykellr please review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Explain what "Stable" label means for OpAMP
4 participants