Eugen
Eugen
Thanks for the report. Indeed, https://github.com/StackStorm/st2chatops#docker is outdated and needs a `README.md` update. We however have https://hub.docker.com/r/stackstorm/st2chatops official docker image available. We'd welcome a Pull Request to update the st2chatops...
To have the environment fully reproducible, running it in existing Docker images from st2chatops repo may help: ```sh docker-compose run xenial npm install --production # example of updating only specific...
`bitops-archive` or `bitops-examples`?
This is a Python SDK, created just a couple of months ago: https://github.com/cdevents/sdk-python
For me, any non-zero works great, as long as we don't report "success" if there was an "error". Even `101`, like we did here https://github.com/bitovi/bitops/blob/dab9410f793a56a37105f6232e11c6616432a3a8/scripts/plugins/utilities.py#L375
Let's add the respective tag then!
Consider ENV variables for the implementation/interface (deploy only this tool).
To me, ENV-only approach reminds of feedback that was highlighted before: "Too many ENV variables, and they're confusing". As a user, there should be an easier way to do things...
With Ops repo generator (`init` CLI argument entrypoint) https://github.com/bitovi/bitops/discussions/353, here is how it all may come together as a consistent CLI: _Proposed_ in #353 OpsRepo generation: ``` docker run \...
Nice. Something like pre-start-hook script, but for the plugins?