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.

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

Ability to convert from one API version schema to another #15

Open
bryantbiggs opened this issue Feb 7, 2023 · 0 comments
Open

Ability to convert from one API version schema to another #15

bryantbiggs opened this issue Feb 7, 2023 · 0 comments
Labels
feature-request Request for a new feature

Comments

@bryantbiggs
Copy link
Member

bryantbiggs commented Feb 7, 2023

Use case

Given a manifest, convert the manifest to the next, stable API version. Some resources only need the API version changed, others will require the schema to be modified to match the new API version

Solution/User Experience

Users should be able to provide a command, either on a per-file basis, or across a directory of files (recursive), searching for the deprecated API version and updating to the next stable version including any schema changes required (where applicable if a mapping is possible)

Possible command(s):

eksup migrate apiextensions.k8s.io/v1beta1 --dir . --recursive
eksup migrate apiextensions.k8s.io/v1beta1 --file manifest.yaml
eksup migrate apiextensions.k8s.io/v1beta1 --dir manifests --recursive --dry-run

Alternative solutions

None
@bryantbiggs bryantbiggs added the feature-request Request for a new feature label Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for a new feature
Projects
Status: Backlog
Development

No branches or pull requests

1 participant