Skip to content

Schedule templating #6

@johrstrom

Description

@johrstrom

One critical thing we're going to need in the future is a 'template' schedule that can be started with some unique key and is identifiable by that key.

Here's a use case: tracking the schedule of a given asset through a video on demand pipeline.

Now, we don't want to create schedules that are basically copy pastes of each other. And what's more is we probably couldn't create them all manually anyhow.

Names and events could be templated like so. The name - being the unique identifier within Deadline - needs to have the id, but also the events it's waiting on tie back to the same asset.
name=asset_pipeline_{{ asset_id }}
event/name/{{ asset_id}} on boarded
event/name/{{ asset_id}} encoded

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions