This was suggested by Jon in the Madrid team-only, and also (perhaps not coincidentally) by Sebastian from Ubuntu.
We cover the debug-* functionality now, but we should add more Pebble/K8s specific debugging, such as getting logs from Pebble, running commands, getting files, and so on.
We should possibly also have a charm debugging skill that utilises both of these.
Also: check if the pebble binary is on the path from Juju and if not, convince the Juju team it should be. Also, can we make it easier to run pebble without the long command line and explicit socket environment variable?
This was suggested by Jon in the Madrid team-only, and also (perhaps not coincidentally) by Sebastian from Ubuntu.
We cover the debug-* functionality now, but we should add more Pebble/K8s specific debugging, such as getting logs from Pebble, running commands, getting files, and so on.
We should possibly also have a charm debugging skill that utilises both of these.
Also: check if the pebble binary is on the path from Juju and if not, convince the Juju team it should be. Also, can we make it easier to run pebble without the long command line and explicit socket environment variable?