Treat archive files and directories as resources?

[ncs-alane]

I have a working design that extracts the archive and manages each file within as a separate resource, which ensures that changes to the extracted package are remediated during convergence. Is this a feature that could be accepted in this cookbook?

[coderanger]

You mean for idempotence tracking? unfortunately that would be both slow and frustrating. Would be better to store stuff externally, like just keep the hashes in a JSON file or something. Seems like a low-benefit change though for very high complexity and adding structural invariants.

I purposefully structured this as non-idempotent except for the URL-based case. It's not perfect but I think it makes it a bit easier to understand at least.

[ncs-alane]

😭

[coderanger]

If you can show how to make it work without being a major perf impact or being brittle, I'm certainly open to look at it :)

[ncs-alane]

🍾