opened
qmateub
username_0
Our to-do list for this bot as we spoke in the tech day demo are:

- Use Docker API to retrieve the stack by name and not retrieve all the stacks and filter in the code by name.
- Use a configuration file (`docker_bot.yml`) for configure parameters that will affect the behaviour of the bot.
- Use the `closed` action for the `pull_requests` scope to delete de stack using the Docker Cloud API after the PR is closed.
- Define a custom template message for the bot (format, structure, etc.)

Any idea is more than welcome 💪
Future plans
issue
created
emmenko
username_1
I think we can now consider this bot to actually do all the work around docker cloud (including e.g. deploying stacks).

### Acceptance criteria
* bot creates a new stack when a PR is opened
  * bot posts the service URLs to the PR after the stack has been created (_this can even be configured to filter out service names_)
* bot updates the stack for each new commit in the PR
  * bot posts a message in the PR about the stack being redeployed (_can be configured_)
* bot deletes the stack when the PR is merged/closed
  * bot posts a message in the PR about the stack being "scheduled" for terminatation (_can be configured_)
comment
created
emmenko
username_1
Which means that in our case we don't need to include this step in the CI anymore.

Additionally, we could also "train" the bot to do something when we mention him (`@docker-cloud-bot`) in a comment (e.g. deploy an additional stack, get extra information, ...).
comment
created
emmenko
username_1
Everything has been implemented now
comment
closed
emmenko
username_1
issue