Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from.
questions: 1. Should this workspace persist between plans run in the same project? 2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules.
A similar thing in puppet was solved by reserving the module name environment. Could be solved for bolt in a better way by having an actual module named say workspace it contains the workspace management features. Just a thought...
Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from.
questions: 1. Should this workspace persist between plans run in the same project? 2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules.