search

walter-cd / walter

Tiny deployment pipeline
http://walter-cd.net
Apache License 2.0
438 stars 39 forks source link

Input/Output for stages and possibly setting pipeline scope variables #96

Closed derekmwright closed 7 years ago

derekmwright commented 9 years ago

Feature request for sending return data from one stage to another. Also, the possibility of setting return output to a pipeline scope variable for usage in later stages.

takahi-i commented 9 years ago

Thank you for the feature request @derekmwright! Walter team will discuss the configuration format and implementation.

jacec commented 9 years ago

:+1: for this. In addition, parameter mappings could drive stage sequencing. i.e. encouraging a declarative approach to the order similar to a Terraform plan.

takahi-i commented 9 years ago

Thank you for the suggestion @jacec! I have made a configuration image for local (pipeline scope) variables and the special variables for using later stages.

https://gist.github.com/takahi-i/de166bde3dece9dab2b5

Any comments would be highly appreciate it @walter-cd/owners.

takahi-i commented 9 years ago

Hi @derekmwright! With Issue #132, Walter supported special variables (OUT, ERR, __RESULT) to use the output of stages in later stages.

seshun commented 8 years ago

It would be nice , if we could pass the data from one stage to another as JSON

eg. _DATA: {"key1":"val1", "key2":"val2"} or _DATA: ["val1","val2"]

mizzy commented 7 years ago

I close this for cleaning issues.