The unfortunate thing about this being supported bywrap() andunwrap() but not bywriteRaster() and theaux.json file is that there may be inconsistent behavior depending on whether an upstream target is skipped or run, whethermemory = "transient" ormemory = "persistent" and whether acrew controller is used or not. It would still be best to not use longnames and varnames in atargets pipeline.

This, I think, is an argument for using something liketerra::wrapCache() like#106. Alternately, perhaps we could issue messages that at least indicate these specific elements will not be preserved and automatically null them out when running a target

Originally posted by@brownag in#141

I know I pushed back against the idea of storing data in a separate cache and just storing metadata (asPackedSpatRasters and the like) in the_targets store, but I do think it would be a good optional strategy, especially if maintaining metadata is important for a workflow.

I'm not sure if this would be a different choice forpreserve_metadata or a separate option. I just wanted to open this issue to make sure it stays on our radar.

Related to#106