Skip to content

only check for env_file#13402

Merged
glours merged 1 commit into
docker:mainfrom
ndeloof:publish_env
Nov 28, 2025
Merged

only check for env_file#13402
glours merged 1 commit into
docker:mainfrom
ndeloof:publish_env

Conversation

@ndeloof
Copy link
Copy Markdown
Contributor

@ndeloof ndeloof commented Nov 27, 2025

What I did

as we publish the raw compose.yaml, there's no need to reject use of environment: the actual value from published environment won't be published. The only env var we could publish are those from env_file(s)

Related issue
fixes #13394

(not mandatory) A picture of a cute animal, if possible in relation to what you did

@ndeloof ndeloof requested a review from a team as a code owner November 27, 2025 13:16
@ndeloof ndeloof requested a review from glours November 27, 2025 13:17
@ndeloof ndeloof force-pushed the publish_env branch 3 times, most recently from d5e011a to 9e7ddb6 Compare November 27, 2025 14:08
@ndeloof
Copy link
Copy Markdown
Contributor Author

ndeloof commented Nov 27, 2025

@glours I'm not sure why we introduced those checks in the first place, as we don't actually publish interpolated values, and we use scanner to detect hard-coded sensitive data.

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
@glours
Copy link
Copy Markdown
Contributor

glours commented Nov 28, 2025

@ndeloof IIRC, the env check was done before we introduced the secret scanner, and I forgot to remove the unnecessary controls.
If there is any issue with this PR, it will be easy to revert it, so let's merge it

Copy link
Copy Markdown
Contributor

@glours glours left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@glours glours merged commit e0977c2 into docker:main Nov 28, 2025
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Inconsistent compose publish behavior with variables

2 participants