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

Allow changing loglevel #2449

Closed
mflendrich opened this issue Feb 4, 2025 · 0 comments
Closed

Allow changing loglevel #2449

mflendrich opened this issue Feb 4, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@mflendrich
Copy link
Collaborator

Issue originally authored by tnozicka as #836

Is this a bug report or feature request?

  • Feature Request

What should the feature do:
Loglvevl should be changable in the API.
We should expose loglevel in the scyllaoperatorconfig for:

  • operator
  • operator sidecar
  • nodeconfigdaemon
  • ...
@mflendrich mflendrich added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Feb 4, 2025
@mflendrich mflendrich mentioned this issue Feb 4, 2025
Closed
@mflendrich mflendrich added the lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. label Feb 4, 2025
@mflendrich mflendrich added good-first-issue Issue that is good as an onboarding task for newcomers and removed good-first-issue Issue that is good as an onboarding task for newcomers labels Feb 11, 2025
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. lifecycle/from-migration Indicates that this issue is a copy of a corresponding issue mentioned in the description. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mflendrich