Barnaby Keene

```json { "level": "error", "ts": "2020-04-13T12:51:51.924Z", "caller": "watcher/git.go:88", "msg": "failed to handle event", "url": "https://github.com/picostack/test", "error": "attempt to handle event for unknown target https://github.com/picostack/test at /data/targets/test" } ``` ``` attempt...

https://docs.aws.amazon.com/sdk-for-go/api/service/secretsmanager/

Package level documentation for go.dev

1

https://pkg.go.dev/github.com/picostack/pico?tab=doc It doesn't need to be all-encompassing, just links out to the Pico project page etc.

Currently, the executor will just copy output from commands to standard out. It may be useful for log aggregation purposes to read this buffer and place each line inside a...

Various Executors for Different Jobs

1

Now that #27 is on the way, the concept of an Executor exists. So far, the only executor is `CommandExecutor` and it just executes `task.Target` jobs. It's a bit misleading...

My main use-case for Pico is to run `docker-compose up -d` for config changes. However, if a container dies for some reason, bringing it back is done in two ways:...

The C should stand for "Container(s)" ;)

To facilitate separating by team/service, config and targets should be cloned recursively by default.

To pair with #10 A CLI would be a no-brainer at this point.