Skip to content

protoxform: remove deprecated fields in v3alpha.#8368

Merged
htuch merged 1 commit intoenvoyproxy:masterfrom
htuch:protoxform-deprecate
Sep 25, 2019
Merged

protoxform: remove deprecated fields in v3alpha.#8368
htuch merged 1 commit intoenvoyproxy:masterfrom
htuch:protoxform-deprecate

Conversation

@htuch
Copy link
Copy Markdown
Member

@htuch htuch commented Sep 25, 2019

We should start tagging messages with "option deprecated = true;" if we
want them to be auto-deprecated by protoxform going forward.

Risk level: Low (v3alpha is not used yet)
Testing: bazel test @envoy_api//..., manual diff inspection.

Signed-off-by: Harvey Tuch htuch@google.com

We should start tagging messages with "option deprecated = true;" if we
want them to be auto-deprecated by protoxform going forward.

Risk level: Low (v3alpha is not used yet)
Testing: bazel test @envoy_api//..., manual diff inspection.

Signed-off-by: Harvey Tuch <htuch@google.com>
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Nice, super cool!

@htuch htuch merged commit e324753 into envoyproxy:master Sep 25, 2019
@htuch htuch deleted the protoxform-deprecate branch September 25, 2019 20:30
danzh2010 pushed a commit to danzh2010/envoy that referenced this pull request Oct 4, 2019
We should start tagging messages with "option deprecated = true;" if we
want them to be auto-deprecated by protoxform going forward.

Risk level: Low (v3alpha is not used yet)
Testing: bazel test @envoy_api//..., manual diff inspection.

Signed-off-by: Harvey Tuch <htuch@google.com>
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.

2 participants