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

Introduce v1beta1 api version #187

Merged
merged 4 commits into from
Jan 10, 2024

Conversation

Danil-Grigorev
Copy link
Contributor

@Danil-Grigorev Danil-Grigorev commented Oct 31, 2023

What this PR does / why we need it:
This change adds v1beta1 api version and conversion webhooks. Does not include any actual changes to the API itself.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #231

Special notes for your reviewer:

Checklist:

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@Danil-Grigorev Danil-Grigorev force-pushed the v1alpha2-api branch 10 times, most recently from 1e2eecf to 1fb2bdb Compare October 31, 2023 17:02
@Danil-Grigorev Danil-Grigorev changed the title [WIP] Introduce v1alpha2 api version Introduce v1alpha2 api version Oct 31, 2023
@Danil-Grigorev Danil-Grigorev added the kind/feature New feature or request label Oct 31, 2023
@richardcase richardcase added this to the v0.3.0 milestone Nov 13, 2023
@richardcase
Copy link
Contributor

Lets update this to v1beta1 (instead of using #230)

Signed-off-by: Danil Grigorev <danil.grigorev@suse.com>
Signed-off-by: Danil Grigorev <danil.grigorev@suse.com>
Signed-off-by: Danil Grigorev <danil.grigorev@suse.com>
@Danil-Grigorev Danil-Grigorev changed the title Introduce v1alpha2 api version Introduce v1beta1 api version Jan 8, 2024
@Danil-Grigorev
Copy link
Contributor Author

@richardcase @salasberryfin The PR is updated and the tests are passing. This v1beta1 api has no changes from the current state of v1alpha1, but if we would change or remove some fields, needed conversions could be added later.

@salasberryfin
Copy link
Contributor

Thanks @Danil-Grigorev. As discussed earlier today, after this is merged, we'll be adapting the changes in #226 so that new fields in the specification are already in `v1beta``.

salasberryfin
salasberryfin previously approved these changes Jan 8, 2024
bootstrap/api/v1alpha1/conversion.go Outdated Show resolved Hide resolved
bootstrap/api/v1alpha1/conversion.go Show resolved Hide resolved
bootstrap/api/v1beta1/conversion.go Show resolved Hide resolved
controlplane/api/v1alpha1/conversion.go Show resolved Hide resolved
controlplane/api/v1beta1/conversion.go Show resolved Hide resolved
controlplane/api/v1beta1/conversion.go Outdated Show resolved Hide resolved
Signed-off-by: Danil Grigorev <danil.grigorev@suse.com>
@Danil-Grigorev
Copy link
Contributor Author

@richardcase All types are added and copyright is updated.

@Danil-Grigorev Danil-Grigorev merged commit c692853 into rancher:main Jan 10, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement v1beta1 API version
3 participants