Simplify local build cycle
Closed this issue · 4 comments
The current instructions for local build and test seem quite manual - would we be open to having an option for spin pluginify (https://github.com/itowlson/spin-pluginify) for local dev? How about if it were in the official plugins registry?
Though it won't currently work because the binary name is different from the plugin name.
Oh shoot, as I so often do, I worked on an approach for this and then took a gander at the issue queue 😂
I'd be willing to update #60 to use spin-pluginify if you think we can get over the hurdle mentioned in #36 (comment).
@vdice spin-pluginify accepts pull requests grin - I think it already knows the plugin name so it should be easy to tweak it to rename a mismatched input binary during tarring? Other ways to make it compatible without changing spin-pluginify:
- Retain the current "copy the binary to have the plugin name" command, and use the copied location in the pluginify manifest (though this would mean the local dev cycle still had that extra manual step)
- Change the name in this project's Cargo.toml from
cloud-plugintocloudso it already has the right name