Remove blueprinted resource when container stopps

[daddeldash]

Summary

I start a docker stack, configured my containers with labels and pangolin creates the resource. Totally fine and works super smooth.
After stopping my stack, the resource in pangolin still exists. This is super when you just want to save resources, but when you are testing something it can really quick make you config a bit messy.

Motivation

Keep the config clean

Proposed Solution

Maybe it is possible to establishe a new label for autoremoving resources after removing the labels from docker

Alternatives Considered

No response

Additional Context

No response

[alvaro17f]

+1

[gomeology]

What if instead of removing the resource, it is just disabled so it's easy to identify in the dash. Or a switch in the dash to enable the delete/non delete feature.... Idk just spit balling

[daddeldash]

I think the best way would be a switch. Turning on auto remove for the resource or turn it off. I also had the case, while playing around with the API, that I deleted a site, but the resource was still there. With this feature, it might also be possible to work around that problem