Skip to content

feature: Evolve an APIResourceSchema From One Version To Another #2014

New issue
New issue
Open
Open
feature: Evolve an APIResourceSchema From One Version To Another#2014
Labels
kind/featureCategorizes issue or PR as related to a new feature.

Description

@stevekuznetsov
stevekuznetsov
opened on Sep 16, 2022

Feature Description

As a service provider, I want to move my provided API from v1alpha1 to v1beta1, changing the schema to add and/or remove fields, and migrating users automatically.

Proposed Solution

Lots of open questions.

Design HackMD
Design Google Doc
Second Google Doc

Alternative Solutions

No response

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Activity

  1. stevekuznetsov
    added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Sep 16, 2022
  2. stevekuznetsov
    assigned
    ncdc
    on Sep 16, 2022
  3. stevekuznetsov
    added this to kcpon Sep 16, 2022
  4. stevekuznetsov
    moved this to New in kcpon Sep 16, 2022
  5. stevekuznetsov
    moved this from New to In Progress in kcpon Sep 16, 2022
  6. ncdc
    removed their assignment
    on Jan 29, 2024
  7. mjudeikis
    moved this from In Progress to New in kcpon Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    • kcp
      Status
      New

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions