Domo - Download Dataset to Platform
Overviewβ
Download any Domo dataset as a csv. The entire dataset will be download, be aware of potential memory constraints if the dataset is very large ( greater than 1M rows).
Either a username/password or an access token should be provided. If both are provided, the access token will be preferred.
Variablesβ
Name | Reference | Type | Required | Default | Options | Description |
---|---|---|---|---|---|---|
Client ID | DOMO_CLIENT_ID | Password | β | - | - | Client ID is generated in the Domo Developer Portal. The ID should have the following scope: data, workflow, user, account, dashboard |
Secret Key | DOMO_SECRET_KEY | Password | β | - | - | The secret attached to the generated Client ID |
DOMO Dataset ID | DOMO_DATASET_ID | Alphanumeric | β | - | - | The id of the dataset desired to be replaced. Can be acquired from the url of the dataset |
Local Destination Folder Name | DOMO_DESTINATION_FOLDER | Alphanumeric | β | - | - | The file path of where the csv should be downloaded to. If left blank, then the file will be saved in the current working directory. |
Shipyard File Name | DOMO_DESTINATION_FILE_NAME | Alphanumeric | β | - | - | The name for the csv file once it is downloaded |
YAMLβ
Below is the YAML template for this Blueprint and can be used in the Fleet YAML Editor.
source:
blueprint: Domo - Download Dataset to Shipyard
inputs:
DOMO_CLIENT_ID: null ## REQUIRED
DOMO_SECRET_KEY: null ## REQUIRED
DOMO_DATASET_ID: null ## REQUIRED
DOMO_DESTINATION_FOLDER: null
DOMO_DESTINATION_FILE_NAME: null ## REQUIRED
type: BLUEPRINT
guardrails:
retry_count: 1
retry_wait: 0h0m0s
runtime_cutoff: 1h0m0s
exclude_exit_code_ranges:
- '101'
- '115'
- '116'
- '201'
- '203'