Ben Hoyt

I think at this point we should simply "solve" this by documenting the existing behaviour -- making clear what exceptions are raised when, and how it's different if `recursive=True`. Related:...

We're planning to look at improving our testing story and documentation in the next cycle, including integration testing. Keeping this open till then.

A doc with significant guidance has been added here: [How to write integration tests for a charm](https://juju.is/docs/sdk/write-integration-tests-for-a-charm). In addition, integration tests are part of the K8s charm tutorial: https://juju.is/docs/sdk/write-integration-tests-for-your-charm

I think this is an interesting idea, but we'd need a concrete proposal to discuss further. I also think the work @PietroPasotti is doing with ops-scenario helps solve this in...

Would be worth seeing what `credential-get` returns on Kubernetes, as that might be a simpler workaround if it does.

@jnsgruk What are your current thoughts on this? I think this is interesting but probably not particularly high priority and perhaps doesn't add enough value to warrant adding new hook...

Let's close this for now then. As discussed, now that we have open-port on K8s trust comes up less often, and even when it's needed, the 3 lines of code...

We've added `containers` for Pebble, but not the other fields in metadata v2, nor `manifest.yaml` -- could still do this for completeness.

This is still worth doing for completeness (though presumably not high priority given lack of people asking for this). I've added the 24.04 label and we'll see if we can...

This is going to be solved by "multi status" or "component status with priority" that we're going to work on this cycle (23.10).