Eventline is now open source and available on GitHub !
Resources are a generic term for components you will use to create pipelines.
Each resource is part of a project and is represented as a YAML document: when deploying a project, all its resources are send to the server. New resources are created, existing resources are updated, and resources which disappeared are deleted.
All resources share the same top-level structure. The following fields are defined:
type: "pipeline" version: 1 name: "website-deployment" description: "deploy website static pages to S3" data: tasks: - name: "generate" task: "generate-static-pages" - task: "deploy" dependencies: - "generate"
version field refers to the data schema used by each resource. In our
previous example, we are using the version 1 of the pipeline data schema. In
the future, we may introduce new versions with different data schemas; when
that happens, previous versions will continue to work as expected.
Each resource is identified by its name. Resource names must be valid API names.
Names are unique by project and by type. This means that you can have both a
task and a command named
send-email in the same project, but you cannot have
two pipelines named `image-analysis'.