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

Compose sub behaviours #198

Open
vishal-biyani opened this issue Sep 5, 2018 · 0 comments
Open

Compose sub behaviours #198

vishal-biyani opened this issue Sep 5, 2018 · 0 comments

Comments

@vishal-biyani
Copy link
Member

Currently compose pre-built in some built in functions like foreach. For example the $.Tasks.DataValidator.Output in below workflow is always a list - which is list of individual outputs of DataValidator.

DataValidator:
    run: foreach
    inputs:
      foreach: "{ output('DataProducer') }"
      do:
        run: cpvalidator
        inputs:
          body: "{ task().Inputs._item }"
    requires:
    - DataProducer

CarpoolAllocator:
    run: cpallocator
    inputs: "{ $.Tasks.DataValidator.Output }"
    requires:
    - DataValidator

In some cases user may want to have a slightly different compose behaviour. For example instead of creating a list of outputs of DataValidator - you may want the CarpoolAllocator be called individually for each output.

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

2 participants