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.

Sign up for GitHub

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

Jump to bottom

Clarify multi api-version support requirements #1128

Open
xirzec opened this issue Aug 2, 2021 · 1 comment
Open

Clarify multi api-version support requirements #1128

xirzec opened this issue Aug 2, 2021 · 1 comment
Assignees
@bterlson
Labels
breaking-change feature MVP v6

Comments

@xirzec
Copy link
Member

xirzec commented Aug 2, 2021

Today we don't have a good understanding of what it means to support multiple api versions in Track 2.

Most data-plane packages sidestep this problem by only supporting the latest apiversion when they are generated. Some convenience clients have carefully crafted models by hand to be version resilient. We need a code-generatable default approach to this.
@xirzec xirzec added the Mgmt This issue is related to a management-plane library. label Aug 2, 2021
@xirzec xirzec mentioned this issue Aug 2, 2021
Open
23 tasks
@sarangan12 sarangan12 added breaking-change feature MVP v6 and removed Mgmt This issue is related to a management-plane library. labels Nov 9, 2021
@sarangan12
Copy link
Member

At this point, it is in very early design phase. But, there might be a possibility that this might result in a breaking change

This was referenced Nov 10, 2021
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bterlson bterlson

Labels
breaking-change feature MVP v6
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bterlson @sarangan12 @xirzec