Skip to content

Conversation

@michaelklishin
Copy link
Collaborator

Sometimes you want a plugin to act as a library
and not an application. That is, for its modules
to be available at compile time and on a running
node but, say, the actual runtime parameter
handling and supervision of shovels to be
handled by another plugin.

Since we do not currently have a concept of
"library plugins" or "library dependencies",
this approach demonstrates one example of how
some plugins can be used effectively as libraries.

Per discussion with @mkuratczyk @Zerpet.

Sometimes you want a plugin to act as a library
and not an application. That is, for its modules
to be available at compile time and on a running
node but, say, the actual runtime parameter
handling and supervision of shovels to be
handled by another plugin.

Since we do not currently have a concept of
"library plugins" or "library dependencies",
this approach demonstrates one example of how
some plugins can be used as libraries.
@michaelklishin michaelklishin added this to the 4.2.0 milestone Aug 25, 2025
@michaelklishin michaelklishin merged commit 5a1bd25 into main Aug 25, 2025
270 of 281 checks passed
@michaelklishin michaelklishin deleted the mk-shovel-library-mode branch August 25, 2025 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants