-
Notifications
You must be signed in to change notification settings - Fork 363
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
Chart UX improvements - schedule.template #90
Comments
Hey @kav sorry for the delay in responding. Are you available to create a PR for this and the other improvements you suggested? They could be separate PRs but also could go altogether. |
BREAKING CHANGE
BREAKING CHANGE Signed-off-by: W. Kavanaugh Latiolais <[email protected]>
There is an additional underlying CRD change required to make template optional but that's out of scope for the chart so I'll leave that to the team to decide on whether template is truly required for the CRD or sensible defaults can be used |
BREAKING CHANGE Signed-off-by: W. Kavanaugh Latiolais <[email protected]>
BREAKING CHANGE Signed-off-by: W. Kavanaugh Latiolais <[email protected]>
BREAKING CHANGE Signed-off-by: W. Kavanaugh Latiolais <[email protected]>
Hey again,
schedules..template should be optional as you can just use the defaults. Also it's a bit non-idiomatic to use keys instead of an array with name properties here.
Let me know if you are interested in PRs for any of this.
The text was updated successfully, but these errors were encountered: