Skip to content
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

Cannot use 0 (zero) for revisionHistoryLimit #308

Closed
dangmai opened this issue Mar 27, 2024 · 1 comment · Fixed by #303
Closed

Cannot use 0 (zero) for revisionHistoryLimit #308

dangmai opened this issue Mar 27, 2024 · 1 comment · Fixed by #303
Assignees
Labels
bug Something isn't working

Comments

@dangmai
Copy link

dangmai commented Mar 27, 2024

Details

What steps did you take and what happened:

With app-template 3.0.4, if you try to set revisionHistoryLimit to 0 in a controller, the generated manifest will actually use the default value (3), probably due to this bug: helm/helm#3164

What did you expect to happen:

I'd expect revisionHistoryLimit in the generated manifest to be correctly set to 0.

There might be other places that use the default function that has this issue inside the code base, I haven't really tried looking for them yet. My use case just happens to use the revisionHistoryLimit property.

Anything else you would like to add:

Additional Information:

@dangmai dangmai added the bug Something isn't working label Mar 27, 2024
@bjw-s
Copy link
Owner

bjw-s commented Mar 27, 2024

👋🏻 Thank you for raising this issue. Something similar was brought to my attention on Discord last week, and a (partial) fix has been implemented in the upcoming 3.1.0 version. I'll try and give it a broader check to see if I can find other places where this behavior could occur.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants