Service is actual execution unit, in order to run any workflow's action or piple task you have use specify : service ID, action, and actual action request.
For instance to copy some assets from S3 to some remote box you can use one of the following:
endly -r=copy
@copy.yaml
pipeline:
transfer:
action: storage:copy
source:
URL: s3://mybucket/dir
credentials: aws-west
dest:
URL: scp://dest/dir2
credential: dest
assets:
file1.txt:
file2.txt: renamedFile2
In this case action selector specifies service:action, while the other keys define action actual request data structure.
endly -w=test
@test.csv
Workflow | Name | Tasks | ||
---|---|---|---|---|
test | %Tasks | |||
[]Tasks | Name | Actions | ||
transfer | %Transfer | |||
[]Transfer | Service | Action | Request | Description |
storage | copy | @transfer | copy asset |
@transfer.yaml
source:
URL: s3://mybucket/dir
credentials: aws-west
dest:
URL: scp://dest/dir2
credential: dest
assets:
file1.txt:
file2.txt: renamedFile2
To get the latest list of endly supported services run
endly -s='*'
To check all actions supported by given service run
endly -s='[service name]'
i.e
endly -s='docker'
To check request/response for service/action combination run
endly -s='[service name]' -a=[action name]
i.e
endly -s='docker' -a='run'
Endly services implement Service interface. The following diagram shows service with its component.
-
System services
-
Cloud services
-
Build and Deployment Services
-
Testing Services
- Validator
- Log Validator Service
- Datastore Preparation and Validation Service
- Endpoint Services
- Runner Services
-
Notification Services
-
Workflow service