The output for resource "init" actions, given the same resource details & type should usually remain the same, since its output mainly reflects the capabilities & requirements of the resource type, not the resource itself.
Therefor, it would probably provide a nice performance boost to be able to cache such results - perhaps using JSON files in the work directory.
The output for resource "init" actions, given the same resource details & type should usually remain the same, since its output mainly reflects the capabilities & requirements of the resource type, not the resource itself.
Therefor, it would probably provide a nice performance boost to be able to cache such results - perhaps using JSON files in the work directory.