-
Notifications
You must be signed in to change notification settings - Fork 85
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
add schedule #317
add schedule #317
Conversation
@AsfaMumtaz validation successful` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're missing updates to the README.md
with this change. It still mentions backup.*
in the values tables.
@@ -1307,7 +1307,7 @@ cronJob: | |||
cpu: 1 | |||
|
|||
# Take backup of application namespace | |||
backup: | |||
schedule: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of schedule
we can be a little more explicit about what this is for in the value's own name.
schedule: | |
backupSchedule: |
What do you think, @AsfaMumtaz?
########################################################## | ||
backup: | ||
schedule: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same suggestion as in the other thread I opened.
I forgot to mention one thing: this changes the interface in a way that is not backwards compatible, so it would require a major version bump. How about instead we detect whether |
No description provided.