-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: PC-13893 Deprecate usage of objective's value field for Composi…
…te SLOs (#295) ## Motivation Currently, we have `value` field required for all objectives in an SLO. We currently allow to not pass that field in YAML at all but it causes it to default to 0 anyway and is returned `value: 0`. This is inconsistent because GET yaml is different than APPLY YAML in such case. Composite SLOs always have exactly one objective, so as such `value` doesn’t matter for them at all as long as it doesn't change. Moreover, the existence of value is documented and used in examples which is confusing to new adopters of Composite SLOs because it is required, changing it will restart budget, but it doesn’t do anything. We want to encourage and allow not setting `value` field for Composite SLOs while maintaining backward compatibility with users who perhaps already explicitly set it. ## Summary `value` field of SLO's `spec.objective` is now optional. `value` is removed from all examples of Composite SLOs. Nobl9 SDK is temporarily redirected unreleased version containing unreleased changes required for this to work. ## Related Changes nobl9/nobl9-go#551 nobl9/nobl9-go#549 nobl9/n9#15406 #312 #295 ## Testing - Describe how to check introduced code changes manually. - Take care of test coverage on unit, integration or end-to-end levels. ## Release Notes Usage of `value` field in schema for `objective` (part of SLO resource) becomes deprecated for objectives using `composite` section. * New Composite SLOs should not set `value` field. * New Composite SLOs will still accept `value: 0` for backward compatibility with older versions of Nobl9 SDK and Nobl9 Terrafrom Provider. * If `value` was previously set to `0` for Composite SLO then it should be omitted going forward. * If `value` was previously set in Composite SLO to a number other than `0` then it can no longer be updated but still will be accepted for backward compatibility. The usage of `value` for SLOs using ratio or threshold SLIs does not change.
- Loading branch information
Showing
7 changed files
with
100 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters