-
Notifications
You must be signed in to change notification settings - Fork 61
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
Define schema in .cue? #20
Comments
@embano1 I think that this is a really interesting idea. PRs are welcome for this if anyone wants to pick it up. I think keeping them in this repo, for now, is fine, and we can move them into their own repo if we decide it's appropriate later. Thanks! |
@ian-bartholomew started working on a prototype schema as proposal. Will file PR once I have all fields covered. |
@embano1 thats amazing, thank you! |
Closes: OpenSLO#20 Signed-off-by: Michael Gasch <mgasch@vmware.com>
Closes: OpenSLO#20 Signed-off-by: Michael Gasch <mgasch@vmware.com>
Created a WIP PR with couple of questions where I'm unclear about the SLO spec. |
@embano1 got it, thanks! |
Can be an alternative to OpenSLO#20 and OpenSLO#87, or as a precursor to them. Changes: - Moved `v1alpha` structs from oslo to here - Created `v1beta1` structs to represent the current state of the spec - Removed `Service` from `v1beta` as it is not used, as far as I could tell - Renamed `kind` to `type` for `AlertCondition` to prevent confusion with `Kind` which has a different meaning
Closes: OpenSLO#20 Signed-off-by: Michael Gasch <mgasch@vmware.com>
I think defining the schema using https://cuelang.org/ would bring a lot of benefits at this early stage of the project, e.g.:
Related: OpenSLO/oslo#23
The text was updated successfully, but these errors were encountered: