theforeman / theforeman/foremanctl
Handle debug logging for troubleshooting
Open
Nobody has claimed this yet.
candlepin
deployment
foreman
foreman-proxy
pulp
- Dominant language
- Python
- Stars
- 27
- Forks
- 47
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 40
Description
Today our installer offers options to increase logging levels and often for specific loggers. How do we handle this in a container world?
Related: https://github.com/theforeman/foreman-quadlet/issues/21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing this issue and the related foreman-quadlet issue 21 to understand the container logging constraints and existing installer logging options. Identify the project entry points that control logging levels and logger selection, then clarify the intended container workflow and acceptance criteria before proposing an implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100