feat(deployments): make spec.revisionHistoryLimit configurable #121
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
Allow setting the spec.revisionHistoryLimit value on Deployment resources to a custom value.
jimeh
force-pushed
the
configurable-deployment-revisionhistorylimit
branch
from
b75b5e4 to
9a149c8
Compare
jimeh
commented
Feb 3, 2024
| @@ -22,7 +22,9 @@ spec: | |||
| type: Recreate | |||
| {{- end }} | |||
| replicas: {{ .replicas }} | |||
| revisionHistoryLimit: 2 | |||
| {{- if (ne (toString $context.Values.mastodon.revisionHistoryLimit) "<nil>") }} | |||
There was a problem hiding this comment.
The use of toString is required to work around a issue with Helm 3.6.0 used in CI, which throws a invalid type error when doing a ne check against nil with a integer value.
|
I'm definitely in favor of more customization. Thank you! |
timetinytim
approved these changes
Feb 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow setting the spec.revisionHistoryLimit value on Deployment resources to a custom value.