Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm generic pipelines (with manifests) #85

Open
1 of 2 tasks
Tracked by #69
tpluscode opened this issue Apr 11, 2023 · 1 comment
Open
1 of 2 tasks
Tracked by #69

npm generic pipelines (with manifests) #85

tpluscode opened this issue Apr 11, 2023 · 1 comment
Assignees

Comments

@tpluscode
Copy link
Contributor

tpluscode commented Apr 11, 2023

Reusable and generic pipelines should be usable in two ways:

  1. Standalone: by loading such a pipeline from the CLI by a node/http URL
  2. Importing from another pipeline (load from more than one ttl file #93)

A prerequisite for the latter will be a generic loader, similar to this

@tpluscode
Copy link
Contributor Author

I've been thinking about this for the case of #98. There, we need the first, standalone style

Rather that addressing by an URL. I was thinking of automatically extending the CLI of barnard59 itself. For example, the "curl" pipeline could be part of barnard59-graph-store. The pipelines could be identified by URI ending in /put, /post etc, thus combining into a dynamic CLI usage

barnard59 graph-store put ...

The additional part would be automatically adding pipeline variables as command line flags...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant