Skip to content

fix: add scope validation on custom resource #348

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

Merged

Conversation

daniellavoie
Copy link
Contributor

@daniellavoie daniellavoie commented Feb 22, 2021

Fixes #339

@metacosm
Copy link
Collaborator

Thank you!

Copy link
Collaborator

@metacosm metacosm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, could you please change the commit message to conform to conventional commit format?
We should also probably remove the reference to upstreaming the checks to the client because I'm actually not sure if it's feasible in that context. We can do it here because we have access to the CRD but the client might not (i.e. it's not a given that the CRD will be retrieved any time a user interacts with the CRs).

@daniellavoie daniellavoie force-pushed the custom-resource-validation branch from 4420239 to eb46a0b Compare February 23, 2021 14:19
@daniellavoie daniellavoie changed the title Validation on Custom Resource interfaces to match CRD definition fix: add scope validation on custom resource Feb 23, 2021
@metacosm metacosm merged commit a0069d9 into operator-framework:master Feb 23, 2021
@metacosm
Copy link
Collaborator

Thanks again!

@daniellavoie
Copy link
Contributor Author

Avec plaisir! :)

@daniellavoie daniellavoie deleted the custom-resource-validation branch February 23, 2021 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

404 page not found on custom resource creation
2 participants