add yes parameter to docker compose up

[londondaintta]

SUMMARY

Add a variable for the docker compose up parameter yes to assume "yes" as answer to all prompts and run non-interactively. This prevents issues where the module hangs if a volume spec changes in the compose file.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

docker_compose_v2

ADDITIONAL INFORMATION

    - name: Start compose environment with yes
      community.docker.docker_compose_v2:
        project_src: compose
        assume_yes: true
        state: present

[felixfontein]

Thanks for your contribution!

The integration test failures are unrelated, the nightly tests were failing as well. (This started yesterday, after the release of Docker Compose 2.33.0.)

The --yes option was added in Compose 2.32.0 (docker/compose#12363).

[felixfontein]

Suggested change

	- When O(yes=true), pass C(--yes) to assume "yes" as answer to all prompts and run non-interactively.
	- When O(yes=true), pass C(--yes) to assume "yes" as answer to all prompts and run non-interactively.
	- Right now a prompt is asked whenever a non-matching volume should be re-created. O(yes=false)
	results in the question being answered by "no", which will simply re-use the existing volume.
	- This option is only available on Docker Compose 2.32.0 or newer.

[londondaintta]

results in the question being answered by "no" is not quite right. It actually causes the command to hang as it waits for stdin.

[felixfontein]

I'm not sure yes is a good option name. One problem is that "yes" is a YAML 1.1 boolean value, so it will require quoting the option to be able to use it (unless Ansible does some magic).

How about approve_questions or something like that?

[londondaintta]

Yes, that's a good point. Perhaps assume_yes is a little more obvious?

[felixfontein]

Could you also add a check to __init__() that self.compose_version >= LooseVersion('2.32.0') when the option is set to true (you'll need from ansible_collections.community.docker.plugins.module_utils.version import LooseVersion)?

[felixfontein]

The integration test failures are unrelated, the nightly tests were failing as well. (This started yesterday, after the release of Docker Compose 2.33.0.)

The problem is actually Docker CLI 28.0.0, which generates some unexpected stderr output. This has been fixed in docker/cli#5854, I hope there will be a bugfix release soon.