log-dir override on agent startup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
It'd be helpful to have a flag we can throw when starting an agent to override the log-dir configured for a host.
This is especially relevant for the Host Manager agent that is setup to control the Docker containers, since it is configured under the Docker "host", though runs directly on the host system. This means the context in which we need to configure the log directory is different for it compared to the rest of the agents in the configuration block.
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
Trace the agent startup path and existing log-dir configuration, then inspect how the Host Manager is launched for the Docker host. Identify the command-line entry point and related configuration handling. Done means an explicit startup flag overrides the configured log directory, including for the Host Manager's host-system context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100