-
Notifications
You must be signed in to change notification settings - Fork 151
feat: Validate DataStores with CEL using the following rules #762
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
Conversation
aerosouund
commented
Mar 28, 2025
- certificateAuthority privateKey must have secretReference or content when driver is etcd
- clientCertificate must have secretReference or content when driver is etcd
- clientCertificate privateKey must have secretReference or content when driver is etcd
- When driver is not etcd and tlsConfig exists, certificateAuthority must be null or contain valid content
- When driver is not etcd and tlsConfig exists, clientCertificate must be null or contain valid content
- When driver is not etcd and basicAuth exists, username must have secretReference or content
- When driver is not etcd and basicAuth exists, password must have secretReference or content
- When driver is not etcd, either tlsConfig or basicAuth must be provided
- certificateAuthority privateKey must have secretReference or content when driver is etcd - clientCertificate must have secretReference or content when driver is etcd - clientCertificate privateKey must have secretReference or content when driver is etcd - When driver is not etcd and tlsConfig exists, certificateAuthority must be null or contain valid content - When driver is not etcd and tlsConfig exists, clientCertificate must be null or contain valid content - When driver is not etcd and basicAuth exists, username must have secretReference or content - When driver is not etcd and basicAuth exists, password must have secretReference or content - When driver is not etcd, either tlsConfig or basicAuth must be provided Signed-off-by: aerosouund <aerosound161@gmail.com>
✅ Deploy Preview for kamaji-documentation canceled.
|
Crediting @tobiasgiese's suggestion:
|
Signed-off-by: aerosouund <aerosound161@gmail.com>
Signed-off-by: aerosouund <aerosound161@gmail.com>
…authority rule Signed-off-by: aerosouund <aerosound161@gmail.com>
Signed-off-by: aerosouund <aerosound161@gmail.com>
@prometherion |
You did a terrific job, @aerosouund: I'll do my best to review this! 🚀 |
Signed-off-by: Dario Tranchitella <dario@tranchitella.eu>
Signed-off-by: Dario Tranchitella <dario@tranchitella.eu>
@aerosouund I just added small changes to your PR, mostly because we weren't running the integration tests upon push events, and also spotted a missed validation to avoid having tests failing on CI. If everything's LGTM and we can merge it. |
@prometherion |