3

Workflow | Chevere

 2 years ago
source link: https://chevere.org/packages/Workflow.html#running-a-workflow
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

# Workflow

The Chevere/Workflow package provides tooling for define an execution procedure based on the workflow pattern (opens new window). Its purpose is to allow to abstract procedure instructions as logic units of interconnected independent async jobs.

👏 With this package you can design a Workflow procedures in a similar fashion to GitHub Actions.

💡 Workflow introduction

Read Workflow for PHP (opens new window) at Rodolfo's blog for a compressive introduction to this package.

# Installing

Workflow is available through Packagist (opens new window) and the repository source is at GitHub (opens new window).

composer require chevere/workflow

# Creating a Workflow

To create a workflow, define the Workflow named jobs. A job is defined by passing an Action class name and its arguments. In the example below, a workflow defines a podcast publishing procedure:

use function Chevere\Workflow\job;
use function Chevere\Workflow\workflow;

workflow(
    process:
        job(
            ProcessPodcast::class,
            payload: '${payload}'
        ),
    optimize:
        job(
            OptimizeFile::class,
            file: '${process:file}'
        ),
    podcast:
        job(
            CreatePodcast::class,
            file: '${optimize:file}',
            request: '${process:request}'
        ),
    releaseTransistorFm:
        job(
            ReleaseTransistorFM::class,
            podcast: '${podcast:object}'
        ),
    releaseApple:
        job(
            ReleaseApple::class,
            podcast: '${podcast:object}'
        ),
    createTranscript:
        job(
            CreateTranscript::class,
            file: '${optimize:file}'
        ),
    translateTranscript:
        job(
            TranslateTranscript::class,
            script: '${createTranscript:script}'
        ),
    notifications:
        job(
            NotifySubscribers::class,
            podcast: '${podcast:object}',
        )
        ->withDepends(
            'releaseTransistorFm', 'releaseApple'
        ),
    tweet:
        job(
            SendReleaseTweet::class,
            fm: '${releaseTransistorFm:url}',
            apple: '${releaseApple:url}',
        )
        ->withDepends(
            'translateTranscript',
        ),
);

For the code above, ${payload} is handled as a workflow variable, the actual value for it should be provided at WorkflowRun layer.

👉 References to previous jobs (as in ${process:file}) implicit declare that the given job depends on the previous process Job as it declares a job response variables.

🦄 Jobs will run in parallel by default. Refer to dependencies for sequential run order.

# Dependencies

Use withDeps method to explicit declare previous jobs as dependencies. The dependent job won't run until the dependencies are resolved.

# Job

The Chevere/Workflow/Job class defines an Action with arguments to pass, supporting direct arguments and variable references to previous jobs response keys.

👉 The action parameter must be a class name implementing the Chevere/Action/Interfaces/ActionInterface. See Action component.

use function Chevere\Workflow\job;

job(action: SomeAction::class, ...$namedArguments);

# Parameters

Parameters for the job are defined in the Action Run.

# Arguments

Arguments can be passed on constructor using named arguments.

use function Chevere\Workflow\job;

job(
    SomeAction::class
    firstName: 'Rodolfo',
    lastName: 'Berrios'
);

For the code above, arguments Rodolfo and Berrios will be passed to SomeAction when running the Workflow. These arguments will be matched against the Parameters defined at SomeAction::run().

# Variables

Referenced arguments can be used to bind arguments against Workflow variables or responses returned by any previous Job.

# Workflow variables

${var} ${workflow_variable}

A Workflow variable, injected by the WorkflowRunner. Regex /^\${([\w]*)}$/.

# Job response variable

${job:key} ${job_name:response_key}

The value for response_key for the job_name job response. Regex /^\${([\w]*)\:([\w-]*)}$/.

# Running a Workflow

To run a Workflow use the Chevere\Workflow\workflowRun function:

use Chevere\Container\Container;
use function Chevere\Workflow\workflow;
use function Chevere\Workflow\workflowRun;

// Your workflow:
$workflow = workflow(/** ... **/);
// Workflow ${variables}
$vars = [
    'payload' => 'the payload'
];
// A PSR-Container for jobs services
$container = new Container();
$run = workflowRun($workflow, $vars, $container);

Variable $run will be assigned to a Chevere\Workflow\Interfaces\WorkflowRunInterface object, which you can query for obtaining data from the workflow runtime.

// TRUE if has a job named `my_job`.
$run->has('my_job');
// A response object for the job's.
$run->get('my_job');

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK