Job parameter accessor ============================================================ When a job (or a component within a job) can be working with a parameterized value, it can rely on a `JobParameterAccessorInterface `__ instance to retrieve that value. .. code-block:: php path->get($jobExecution); // do something with $path } } What types of parameter accessors exists? ------------------------------------------------------------ **Built-in parameter accessors:** * `ChainParameterAccessor `__: try multiple parameter accessors, the first that is not failing is used. * `ClosestJobExecutionAccessor `__: try another parameter accessor on each job execution in hierarchy, until not failed. * `DefaultParameterAccessor `__: try accessing parameter using another parameter accessor, use default value if failed. * `JobExecutionParameterAccessor `__: extract value from job execution’s `parameters `__. * `JobExecutionSummaryAccessor `__: extract value from job execution’s `summary `__. * `ParentJobExecutionAccessor `__: use another parameter accessor on job execution’s parent execution. * `ReplaceWithVariablesParameterAccessor `__: use another parameter accessor to get string value, and replace variables before returning. * `RootJobExecutionAccessor `__: use another parameter accessor on job execution’s root execution. * `SiblingJobExecutionAccessor `__: use another parameter accessor on job execution’s sibling execution. * `StaticValueParameterAccessor `__: use static value provided at construction. **Parameter accessors from bridges:** * From ``symfony/framework-bundle`` bridge: * `ContainerParameterAccessor `__: use a parameter from Symfony’s container. .. seealso:: | :doc:`What is a job? ` | :doc:`When does a job execution hierarchy is created? ` | :doc:`What is a job execution? `