Move towards installable / PATH based scripts

[JimCircadian]

The current instructions are unwieldy and manually triggering scripts annoying. I would like to make this much more intuitive to use:

• Ensure scripts can be used via PATH resolution to /scripts/
• Ensure scripts can be installed independently of the pipeline directory: that is the /scripts/ directory is effectively arbitrary
• Look at a suitable packaging and deployment mechanism for pipeline that allows initialisation of pipelines via command, not via clone

[JimCircadian]

Keen to inherit some of the structure / approach taken for the AMOP project at BAS with the simple-action-pipeline. Is there convergence afoot @matscorse? Would be lush to talk to you about that potential down the line

[matscorse]

Yes @JimCircadian , I will take a look at the icenet pipeline as you identify above and think about possible application of simple-action-pipeline. This could also bring a new features into simple-action-pipeline.

[bnubald]

@JimCircadian Thanks for raising this.

@matscorse If looking into this, please have a look at the v0.4.0 branch mentioned in the milestone in this issue. For up to this version, we'll stick with the existing approach.

https://github.com/icenet-ai/icenet-pipeline/tree/v0.4.0_dev

But, can we not use existing tools out there for these use cases such as MLflow? - once we reached convergence with v0.4.0, using something like this was on my mind.