Sign in

v1

latestOpenAPI 3.0.3Apache 2.02026-07-17302459.9 KB
Data Jobs Deployment

Get Data Job deployments. | (Stable)

<i>(Introduced in v1.0)</i>

get/data-jobs/for-team/{team_name}/jobs/{job_name}/deployments

Query parameters

deployment_idstring

Get the Deployment with this id (e.g production, staging, dev)

mode'testing' | 'release'

The execution mode that the data job is deployed in. Data Jobs used for development or testing purposes are marked as testing. This is used by Operations team on platform rollout and infrastructure changes adoption. For example, rollout and validation of testing jobs first, then proceeding with release data jobs. Also, testing and release jobs may have different limits and SLA targets.

Example:release

Get Deployments only for this mode.

Response

A list of data job deployments

vdk_versionstring

A specific VDK version to use

job_versionstring

Job version (can be Git commit)

python_versionstring

A python release version (supported by the service) to be used for job deployments.

mode'testing' | 'release'

The execution mode that the data job is deployed in. Data Jobs used for development or testing purposes are marked as testing. This is used by Operations team on platform rollout and infrastructure changes adoption. For example, rollout and validation of testing jobs first, then proceeding with release data jobs. Also, testing and release jobs may have different limits and SLA targets.

idstring

String that identifies a single deployment of a Data Job. Currently only one single deployment per Data Job is possible.<br> In the future:<br> It's recommended to use following ids - development, testing, production. However users are free to come up with their own. For example, this enables the creation of 3 different deployments, using the same Data Job code:<br> development deployment --deployment-id development<br> testing deployment --deployment-id testing<br> production deployment --deployment-id prod

enabledboolean

Enable/disable flag

last_deployed_datestring

The date and time in UTC of the last deployment of the data job

last_deployed_bystring

The username of the user who modified the data job last

Example response

[
  {
    "job_version": "11a403ba",
    "python_version": "3.9",
    "mode": "release",
    "id": "release",
    "contacts": {
      "notified_on_job_failure_user_error": [
        "auserov@example.mail.com"
      ],
      "notified_on_job_failure_platform_error": [
        "auserov@example.mail.com"
      ],
      "notified_on_job_success": [
        "auserov@example.mail.com"
      ],
      "notified_on_job_deploy": [
        "auserov@example.mail.com"
      ]
    },
    "schedule": {
      "schedule_cron": "0 0 13 * 5"
    },
    "resources": {
      "cpu_request": 10,
      "cpu_limit": 20,
      "memory_request": 1024,
      "memory_limit": 2048
    },
    "last_deployed_date": "2021-02-02T10:50:40.034Z",
    "last_deployed_by": "jdoe"
  }
]