ExtendoHub CLI

eh, the ExtendoHub CLI supports extension development making it easy to develop and test extensions locally and interact with ExtendoHub services (e.g., logging).

eh can be installed using npm as a global (or local) command using

npm i -g @extendohub/cli

Scenario

Debug user code

User is developing an extension and wants to debug/iterate. Use the CLI to run their code.

• Code: local
• Compute: "local" (as in not in Fly) so we can step through in debugger
• Params: Here we need the params as they would be sent to the compute service (e.g., JavaScript or Image, ...). We may not expose all of the gory bits to the user
  • ??? what level of params we need here. Compute or Service (e.g., JavaScript)? We are going to trigger the "runtime" which is pretty low level. Perhaps we need a local Compute
  • Compute level params come from generator, harvested from previous runs, or a manually authored (or some combo of these)

Try user code

User is doing web based development and want to try their code (e.g., Click the Run button) and see the output. This is largely the same as debug/CLI scenario but no debug.

• Code is in the browser's editor (so technically on the user's machine)
• Compute is hosted by ExtendoHub
• Compute level params come from generator, harvested from previous runs, or a manually authored (or some combo of these)

Trigger installed extension for real

• For example, run the midnight worker in Hubble

• Final validation that the deployed thing works

• Extension is determined by normal extension point logic

• Code comes from installed extension