Skip to content

doc: updated procedure of adding v2 proto config files for extensions#10667

Closed
cpakulski wants to merge 1 commit intoenvoyproxy:masterfrom
cpakulski:api-docs
Closed

doc: updated procedure of adding v2 proto config files for extensions#10667
cpakulski wants to merge 1 commit intoenvoyproxy:masterfrom
cpakulski:api-docs

Conversation

@cpakulski
Copy link
Copy Markdown
Contributor

Description:
There is a new option required for proto versioning:
option (udpa.annotations.file_status).package_version_status.
Without that option v2 proto config files are not included in a build.
Updated doc describing procedure of adding v2 config files for extensions.
Risk Level:
Low
Testing:
None
Docs Changes:
None
Release Notes:
None

option (udpa.annotations.file_status).package_version_status = ACTIVE; must be added.

Signed-off-by: Christoph Pakulski <christoph@tetrate.io>
@repokitteh-read-only
Copy link
Copy Markdown

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #10667 was opened by cpakulski.

see: more, trace.

@htuch
Copy link
Copy Markdown
Member

htuch commented Apr 6, 2020

@cpakulski we're about to switch to v3 being the active API, I'll copy and update your patch into #10636. Thanks for providing this.

@htuch htuch closed this Apr 6, 2020
@htuch htuch reopened this Apr 6, 2020
htuch added a commit to htuch/envoy that referenced this pull request Apr 6, 2020
Signed-off-by: Harvey Tuch <htuch@google.com>
@htuch htuch closed this Apr 6, 2020
@cpakulski cpakulski deleted the api-docs branch December 14, 2020 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants