avast/gradle-docker-compose-plugin

Suggestion - use --no-log-prefix when captureContainersOutputToFiles is specified

Open

#465 opened on Nov 14, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Groovy (429 stars) (103 forks)batch import
help wanted

Description

When using captureContainersOutputToFiles, the plugin generates a log file per service, which makes the the log prefix redundant and the logs harder to read. Could we pass --no-log-prefix in that case or at least provide a logsAdditionalArgs setting to make that possible?

Contributor guide

Tech stack
docker
Domain
devopsbuild systemtesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Gradle plugin basicsDocker Compose knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the plugin's source code, particularly the task configuration class where docker compose commands are assembled. Look for where ` log prefix` is added and consider either adding a `logsAdditionalArgs` setting or conditionally passing ` no log prefix` when `captureContainersOutputToFiles` is enabled. Review existing tests for similar feature flags to guide implementation.