This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Fixed rollback.timeout type definition in CRD
#2251
Merged
Conversation
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
Trying to a apply a `HelmRelease` with a set `rollback.timeout` would result in a validation error: `spec.rollback.timeout in body must be of type int64: "integer"`. This was due to the fact that the validation scheme definition contained a mistake, the `type` should be `integer` and the format is `int64`.
squaremo
approved these changes
Jul 15, 2019
There was a problem hiding this comment.
Yep -- checked against https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#data-types
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Trying to a apply a
HelmReleasewith a setrollback.timeoutwouldresult in a validation error:
spec.rollback.timeout in body must be of type int64: "integer".This was due to the fact that the validation scheme definition contained
a mistake, the
typeshould beintegerand the format isint64.Fixes #2250