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.

Sign up for GitHub

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

Jump to bottom

Reevaluate non-optional or defaulted fields in manager task spec #1869

Open
Tracked by #1939
rzetelskik opened this issue Mar 28, 2024 · 0 comments
Open
Tracked by #1939

Reevaluate non-optional or defaulted fields in manager task spec #1869

rzetelskik opened this issue Mar 28, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@rzetelskik
Copy link
Member

What should the feature do?

Currently most of the attributes of manager task specs are non-optional and/or defaulted. We should reevaluate how these attributes interact with each other and which of them can and should be made optional and non-defaulted.

/kind feature
/priority important-longterm

What is the use case behind this feature?

ditto

Anything else we need to know?

No response
@rzetelskik rzetelskik added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 28, 2024
@scylla-operator-bot scylla-operator-bot bot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Mar 28, 2024
@rzetelskik rzetelskik mentioned this issue Mar 28, 2024
Merged
@tnozicka tnozicka mentioned this issue Apr 16, 2024
Closed
@rzetelskik rzetelskik mentioned this issue May 24, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rzetelskik