You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
External modules can now be launched by tt from the modules folder in the project. However, these are currently limited to executables (binaries or scripts) without an additional running context.
Additionally, we lack a method for distributing external modules to users, but we aim to establish one.
The RFC should address these challenges by outlining a process for writing and distributing external modules. It should include:
The execution context available to external modules and instructions on how to process it (it could be just a list with environment variables, current project path, config file path, args etc)
A description of where module source files should be stored
Guidance on where and how to upload the finalized artifacts
How these modules will be delivered to customers
The text was updated successfully, but these errors were encountered:
External modules can now be launched by
tt
from themodules
folder in the project. However, these are currently limited to executables (binaries or scripts) without an additional running context.Additionally, we lack a method for distributing external modules to users, but we aim to establish one.
The RFC should address these challenges by outlining a process for writing and distributing external modules. It should include:
The text was updated successfully, but these errors were encountered: