Can I turn off Engine GC and manually manage cleanup?

[hard ingot]

I (ofc) have a weird use-case pattern. (need to keep unpublished layers around, stopgap for proper persistence support)

1. If I turn of GC and do nothing, I should be ok in terms of not losing stuff, might just fill my disk?
2. Will the Go SDK EngineCache/Entry allow me to manually clean up in a targeted way?

[versed jungle]

1. yes, correct
2. not currently the prune command currently prunes everything and doesn't allow you specify an entry to prune

the PruneInfo sturct here https://github.com/dagger/dagger/blob/8278b0e451cac3376307d2574dab65c20a69d426/engine/server/gc.go?plain=1#L73 has a way to define filters but we're not currently exposing those through the API. Not sure if this would make sense so users could have a more fine-grained control on what to prune

cc @true beacon

[hard ingot]

If persistence is going to be a thing, we will also need a way to clean up based on our business logic, which is also what I need here

[versed jungle]

If persistence is going to be a thing,

mind expanding on this one?

[heavy scaffold]

Persistence via environments will solve that. Because by definition your environment will only contain what you want to persist.