Attributes of Depot YAML Configuration¶
Structure of Depot YAML¶
name: ${{depot-name}}
version: v2alpha
type: depot
description: ${{description}}
tags:
- ${{tag1}}
- ${{tag2}}
owner: ${{owner-name}}
layer: user
depot:
type: ${{source-type}}
external: ${{true}}
compute: ${{runnable-default}}
secrets:
- name: ${{abfss-instance-secret-name}}-r
allkeys: true
- name: ${{abfss-instance-secret-name}}-rw
allkeys: true
${{source-type}}:
name: mydepot
version: v2alpha
type: depot
description: abfss connection
tags:
- abfss
owner: iamgroot
layer: user
depot:
type: ABFSS
external: true
compute: runnable-default
secrets:
- name: abfss-instance-secret-r
allkeys: true
- name: abfss-instance-secret-rw
allkeys: true
abfss:
account: ${{account-name}}
container: ${{container-name}}
relativePath: ${{relative-path}}
format: DELTA # ICEBERG or DELTA
Attributes Configuration¶
name¶
Description: Declare a name for the Depot.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | mandatory | none | alpha numeric values with the RegEx [a-z0-9]([-a-z0-9]*[a-z0-9]); a hyphen/dash is allowed as a special character total length of the string should be less than or equal to 48 characters names of cluster & depot have a different RegEx [a-z]([a-z0-9]*); a hyphen/dash is not allowed as a special character |
Example usage:
version¶
Description: The version of the Resource
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | mandatory | none | v1, v2alpha |
Example usage:
type¶
Description: Provide the value for the Resource type.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | mandatory | none | cluster, compute, depot, policy, secret, service, stack or workflow |
Example usage:
tags¶
Description: Assign tags to the Resource-instance
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| mapping | mandatory | none | any string; special characters are allowed |
Example usage:
description¶
Description: Assign description to Resource
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | none | any string |
Additional information: the description can be within quotes or without.
Example usage:
owner¶
Description: Identification of the user
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | id of the user applying the Resource | any valid dataos user id |
Additional information: when no ID**** is provided, or an incorrect ID is provided, the system automatically corrects it to the ID of the user who applied the Resource on DataOS CLI
Example usage:
layer¶
Description: Declare the name of the layer in which the Resource is going to be deployed
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | user | user/system |
Additional information: From a user's perspective, the operating system can be envisaged as working at two levels - user layer & system layer. This is only a logical separation to understand the workings of the system.
Example usage:
depot¶
Description: specifies the configuration for the Depot section
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| mapping | mandatory | none | none |
Example Usage:
type¶
Description: Specifies the type of Depot
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | mandatory | none | ABFSS, WASBS, REDSHIFT, S3, ELASTICSEARCH, EVENTHUB, PULSAR, BIGQUERY, GCS, JDBC, MSSQL, MYSQL, OPENSEARCH, ORACLE, POSTGRES, SNOWFLAKE |
Example Usage:
description¶
Description: Provides a description for the Depot
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | none | any string |
Example Usage:
external¶
Description: Specifies whether the depot is external. Set to true if the depot is external
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | mandatory | false | true/false |
Example Usage:
source¶
Description: Maps the depot to the metadata source name in Metis. Running a scanner job on this depot will save the metadata in Metis DB under the specified 'source' name. If this key-value property is not mentioned, the metadata will surface under the depot name on Metis UI.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | depot name | any string |
Example Usage:
compute¶
Description: Specifies the compute resource for the depot being created.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| string | optional | runnable-default | any Compute Resource |
Example Usage:
secrets¶
Description: Specifies the cInstance Secret reference of the data source.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| mapping | optional | none | varies between data sources |
Example Usage:
secrets:
- name: ${{abfss-instance-secret-name}}-r # Name of the read-only Instance Secret
allkeys: true # Use all keys from this secret
- name: ${{abfss-instance-secret-name}}-rw # Name of the read-write Instance Secret
allkeys: true # Use all keys from this secret
secrets.name¶
The 'name' attribute specifies the name of the Instance Secret to be used for authentication.
secrets.allkeys¶
The 'allkeys' attribute, when set to true, indicates that all keys within the referenced Instance Secret are available for use.
${{depot-type}}¶
Description: Specifies the precise location of the data and provides the hierarchical structure in which the data is stored.
| Data Type | Requirement | Default Value | Possible Value |
|---|---|---|---|
| mapping | mandatory | none | varies between data sources |
Example Usage: