Very important to distinguish here...
You cannot hot reload the same nar (same component version info in the
manifest). However, you can hot load additional new versions and select
them in the UI. If you're tossing a new copy of the nar with the same
manifest metadata in the lib it wont see it
I confirmed previously that autoload applies to an initial load and won't
hot-reload on NAR update (instead requires an instance restart).
If the custom component doesn't come up, I'm pretty sure there was a
problem with dependency resolution. Check the startup logs for errors and
any WARN
Hello!
I am looking for guidance on an issue I am facing concerning utilizing the
autoloading of custom processors using the extensions directory.
The issue is with autoloading custom processor NARs and being able to see them
in the UI without a restart of the docker container. I can confirm
