Fixing rm command and API…

[vdemeester]

… to behave more like docker-compose. Fixes #129 🐝.

$ libcompose-cli ps
# […]
Name           Command                         State         Ports
compose_db_1   /docker-entrypoint.sh postgres  Up 8 seconds  5432/tcp
compose_web_1  nginx -g 'daemon off;'          Up 8 seconds  443/tcp, 80/tcp
$ libcompose-cli rm
# […]                      
No stopped containers
$ libcompose-cli stop db
# […]
$ libcompose-cli rm
# […]
Going to remove compose_web_1, compose_db_1
Are you sure? [yN]

As docker-compose it will try to remove only containers that are stopped. And the --force flag is used to skip the confirmation only 🐞.

$ libcompose-cli stop db
# […]
$ libcompose-cli rm --force
# […]                  
Going to remove compose_db_1
$ libcompose-cli ps
# […]
Name           Command                 State          Ports
compose_web_1  nginx -g 'daemon off;'  Up 54 seconds  443/tcp, 80/tcp

It's not really done yet :

• Probably should add some log/information of each container removed (like docker-compose does). This should be handled widely on the cli I think.
• Should add more integration tests (making sure we don't remove non-stopped containers, etc…).

🐸

Signed-off-by: Vincent Demeester vincent@sbr.pm

[vdemeester]

/ping @dnephin @ibuildthecloud

[dnephin]

I don't think we want Force: true. We're already checking if it's stopped, so we shouldn't need to force it.

[vdemeester]

Oh you're right 😝.

[vdemeester]

@dnephin Updated, rebased and added an integration tests.

[dnephin]

LGTM