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

Support CRD plural name checking in crddiff #89

Open
ulucinar opened this issue Apr 4, 2023 · 0 comments
Open

Support CRD plural name checking in crddiff #89

ulucinar opened this issue Apr 4, 2023 · 0 comments
Labels
enhancement New feature or request is:triaged
Milestone

Comments

@ulucinar
Copy link
Contributor

ulucinar commented Apr 4, 2023

What problem are you facing?

In a recent issue, the plural names of some resources have changed and this resulted in broken upgrades from the previous versions of the provider. With the current state of our tooling and architecture, we cannot properly handle such changes without requiring some manual intervention.

How could Uptest help solve your problem?

It would be wise to extend crddiff to report such changes in a blocking mode up until we evolve our tooling to be able to cope with such changes. crddiff already has the previous & current versions of a CRD in its context and thus we can extend crddiff to check for plural name changes in addition to the spec.forProvider & status.atProvider breaking API checks (currently acting as a non-blocking linter for these checks).

@jeanduplessis jeanduplessis added this to the 1.0 milestone Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request is:triaged
Projects
None yet
Development

No branches or pull requests

2 participants