Hi team, are we planning to add support for installing plugins locally using the automation API ? cc @little-cartoon-10569

I'm trying to imagine a use case. As I understand it, in order to run the automation-api program, you need to run

npm install

or the equivalent for your runtime. And that process installs the plugins. So by the time automation-api is running, the plugins are installed. Is this not what you're seeing? What is the problem you're looking to solve?

Actually it’s more of a dev workflow. I haven’t published the provider and will be making changes but when using automation API to create the stack using the resources managed by local provider, I have no option to load the plugin through the automation API itself.

And you can't install it using the runtime's normal package installation functionality? Just from a local repository? Another option would be to update your "build-and-install-locally" script on the plugin side to include copying it to the local plugin directory if it exists.

Thanks for this tenwit. I think the script to copy the plugin to plugin cache would work.

FWIW I'm having this same issue. Glad I found this discussion! I'll copy the plugin to my cache

I did the same and in the naming scheme it expects and it worked nicely. So confirming it works !!

did you copy a .lock file or anything?

Nope, I didn’t

Thanks! will give it a shot

Cool, do revert if any issues and I’ll double check if I did anything different