Skip to content

fix(compose): make sure any flags defined for compose up also exist for compose down #102

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.

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

Closed
wants to merge 1 commit into from

Conversation

fiam
Copy link
Contributor

@fiam fiam commented Jun 24, 2025

When compose calls the model provider, the same arguments are passed to both compose
up and compose down. Unless compose down supports any flag supported by compose up, some
of these flags will cause a parsing error and cause compose down to fail.

To fix this, move the flag setup to a dedicated type and function that can be shared
by both commands.

Signed-off-by: Alberto Garcia Hierro damaso.hierro@docker.com

@xenoscopic
Copy link
Contributor

CC @glours @ndeloof for their opinion / review.

…or compose down

When compose calls the model provider, the same arguments are passed to both compose
up and compose down. Unless compose down supports any flag supported by compose up, some
of these flags will cause a parsing error and cause compose down to fail.

To fix this, move the flag setup to a dedicated type and function that can be shared
by both commands.

Signed-off-by: Alberto Garcia Hierro <damaso.hierro@docker.com>
@fiam fiam force-pushed the alberto/fix-missing-flags branch from 2e43517 to 0bf514a Compare June 25, 2025 08:10
@xenoscopic xenoscopic requested review from ndeloof and glours June 25, 2025 22:37
@doringeman
Copy link
Collaborator

Have you encountered an issue wrt this change @fiam?

I've been told that ⬇️ .

compose uses metadata command to know those who apply to up or down

@xenoscopic
Copy link
Contributor

xenoscopic commented Jun 26, 2025

Now that we've merged #77, maybe this will be fixed automatically.

Note that we haven't actually tagged / shipped #77 yet, but will before tomorrow.

@fiam fiam closed this Jun 26, 2025
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.

3 participants