Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Conversion, store and serving of v1beta1 APIs #615

Closed
nachocano opened this issue Mar 6, 2020 · 2 comments · Fixed by #871
Closed

Conversion, store and serving of v1beta1 APIs #615

nachocano opened this issue Mar 6, 2020 · 2 comments · Fixed by #871
Assignees
Labels
area/api APIs kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/1
Milestone

Comments

@nachocano
Copy link
Member

Problem
Once we have the v1beta1 APIs #614, we need to add the proper conversion mechanism, and start serving them.

Persona:
Developer

Exit Criteria
Serving v1beta1 APIs and provide conversions if needed

Additional context (optional)
knative/eventing#2508

@nachocano nachocano added release/1 priority/1 Blocks current release defined by release/* label or blocks current milestone kind/feature-request New feature or request area/api APIs labels Mar 6, 2020
@nachocano nachocano added this to the v0.14.0-M2 milestone Mar 17, 2020
@nachocano
Copy link
Member Author

When we start serving v1beta1, I think we will break gcloud integration.
We should make sure we are not. We should have the gcloud E2E tests in place before doing so.
#556

@nachocano
Copy link
Member Author

my apologies, I was too optimistic, won't be able to make this in the three days I have remaining.
/unassign

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/api APIs kind/feature-request New feature or request priority/1 Blocks current release defined by release/* label or blocks current milestone release/1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants