-
Notifications
You must be signed in to change notification settings - Fork 461
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
Operator UI allows creation of Tenant without required Encryption fields #1610
Comments
Something cannot work, see go-openapi/validate#152 |
Yes. But the backend is where the data is finally validated. I am not good at frontend by the way. Right now it's not submittable, the backend will return an error but it won't show the error either, if you're good at front-end, you can help with that. |
thanks, I'll reopen the issue then. Thanks @jiuker for adding a validation. |
Actually it was already there, it just didn't take effect, I went and submitted a pr to valid to fix the problem |
closing this since operator ui has been deprecated, see https://github.com/minio/operator/blob/master/docs/notes/v6.0.0.md#whats-new for more |
If I write something on the Encryption fields, the Create button is disabled until all fields are set but if I started setting up some fields and I change between encryption methods, the Create button gets enabled and allows us to create a Tenant. Which then causes an error while trying to initialize it. I think we probably need to refresh the button state every time we change encryption methods.
Screen.Recording.2023-05-22.at.10.24.14.AM.mov
Since it allows the creation of the tenant, it fails while creating the KES pod

Expected Behavior
Created button should be disabled if Encryption is Enabled and not all fields are being set.
Created button state should be refreshed if changing encryption method and fields should also be refreshed to empty values.
Current Behavior
Encryption fields hold value even after changing encryption method
Possible Solution
Refresh button state on change of encryption method
Steps to Reproduce (for bugs)
Context
Regression
Your Environment
minio-operator
): v5.0.4uname -a
):The text was updated successfully, but these errors were encountered: