* Ignore result of idempotency test since this seems like a hopeless cause...
* And another one.
(cherry picked from commit 68993fe353)
Co-authored-by: Felix Fontein <felix@fontein.de>
* Adjust 'report this' messages to only report if the latest version still has this problem. (#1173)
(cherry picked from commit 6b5d76bdee)
* Adjust checks.
(cherry picked from commit 24f35644e3)
* Since docker-compose 2.32.2 present_3 is no longer changed.
This has been caused by https://github.com/docker/compose/pull/12442,
since that PR removes the "building" event.
* Remove deprecated 'version' fields.
* Catch more warnings that shouldn't be there.
* Add explicit handling of dry-run image build JSON events.
These produce some one-off ID values that don't make any sense as ID values.
* Use simple-1 image instead of Alpine image for docker_compose_v2_pull tests.
* Use simple-1 image instead of Alpine image for docker_compose_v2 pull tests.
* Allow to specify inline compose definitions.
* Remove comma that trips Python 2.7.
* Add tests.
* Add PyYAML as EE dependency.
* Be more explicit on PyYAML.
* Add pull option for 'docker compose up'.
* Improve dry-mode event parsing, and also parse pull-related events.
* Improve error handling, and add first tests.
* Fix action status documentation.
* Add more tests.
* Always return stderr.
This makes debugging misbehavior a lot easier since you can see
what 'docker compose' actually returned.
* Reformat existing tests.
* Add docker_compose_v2 module.
* Add note on compatibility.
* Parse more events.
Emit warnings (or things we assume are warnings), and report unparsable
messages to the user so they can report them to us.
