Using values from environment variables
The configuration file allows substitutions with environment variables. For example:COGNITE_CLIENT_SECRET environment variable into the cognite/secret parameter. You can also do string interpolation with environment variables, for example:
Implicit substitutions only work for unquoted value strings. For quoted strings, use the
!env tag to activate environment substitution:Using values from Azure Key Vault
The DB extractor also supports loading values from Azure Key Vault. To load a configuration value from Azure Key Vault, use the!keyvault tag followed by the name of the secret you want to load. For example, to load the value of the my-secret-name secret in Key Vault into a password parameter, configure your extractor like this:
azure-keyvault section in your configuration, with the following parameters:
Example:
Base configuration object
cognite
Global parameter.
Describes which CDF project the extractor will load data into and how to connect to the project.
idp-authentication
Part of cognite configuration.
Insert the credentials for authenticating to CDF using an external identity provider (IdP), such as Microsoft Entra ID (formerly Azure Active Directory).
scopes
Part of idp-authentication configuration.
Enter the list of scopes requested for the token.
Each element of this list should be a string.
certificate
Part of idp-authentication configuration.
Authenticate with a client certificate.
data-set
Part of cognite configuration.
Enter a data set into which the extractor should write data.
extraction-pipeline
Part of cognite configuration.
Enter the extraction pipeline for remote config and reporting statuses.
connection
Part of cognite configuration.
This parameter configures the network connection details.
proxies
Part of connection configuration.
Input the dictionary mapping from protocol to URL.
logger
Global parameter.
Sets up logging to a console and files. This is an optional value.
console
Part of logger configuration.
Include the console section to enable logging to standard output, such as a terminal window.
file
Part of logger configuration.
Include the file section to enable logging to a file. The files are rotated daily.
extractor
Global parameter.
Contains the common extractor configuration.
state-store
Part of extractor configuration.
Include the state store section to save extraction states between runs. Use a state store if data is loaded incrementally. We support multiple state stores, but you can only configure one at a time.
raw
Part of state-store configuration.
Stores the extraction state in a table in CDF RAW.
local
Part of state-store configuration.
Stores the extraction state in a JSON file on the local machine.
source
Global parameter.
Insert the source configuration for data mirrored from Fabric.
raw-tables
Part of source configuration.
Input the list of raw tables to be ingested.
Each element of this list should be a cDF RAW configuration
destination
Global parameter.
Insert the destination configuration for time series data mirrored from Fabric.
subscriptions
Global parameter.
Insert the time series subscriptions configuration for time series mirrored to Fabric.
Each element of this list should be a cDF time series sync to CDF configuration
partitions
Part of subscriptions configuration.
Enter the List of partitions to be ingested.
Each element of this list should be an integer.