-
Notifications
You must be signed in to change notification settings - Fork 14
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
[issue-172] Adds flag success-build-history-limit
and failed-build-history-limit
#334
Conversation
I actually think we shouldn't set a default via the CLI, if the flag isn't provided, we should leave that field null. My opinion is that defaults should only be applied in one place, and that place is usually the kpack webhook controller. This way, the actual value can differ between kpack versions and in the distant future might even be configurable at the cluster level without ever having to upgrade the CLI. |
abfac5a
to
9e68bfe
Compare
To set values to null I had to change the |
d171c9d
to
5e0f509
Compare
5bde8d1
to
3f884dd
Compare
@fcaroline2020 needs rebasing |
…description, adds both commands to `patch` Signed-off-by: Caroline Scherf <[email protected]>
3f884dd
to
7c4fe51
Compare
success-build-history-limit
andfailed-build-history-limit
to image create, save, patchresolves #172
resolves #244