List of required configuration parameters for the Google Drive to S3/ADLS ReadyFlow

When deploying the Google Drive to S3/ADLS ReadyFlow, you have to provide the following parameters. Use the information you collected in Prerequisites.

Table 1. Google Drive to S3/ADLS ReadyFlow configuration parameters
Parameter name	Description
CDP Workload User	Specify the Cloudera machine user or workload username that you want to use to authenticate to the object stores. Ensure this user has the appropriate access rights to the object store locations in Ranger or IDBroker.
CDP Workload User Password	Specify the password of the Cloudera machine user or workload user you are using to authenticate against the object stores (via IDBroker).
Destination S3 or ADLS Path	Specify the name of the destination S3 or ADLS path you want to write to. Make sure that the path starts with "/".
Destination S3 or ADLS Storage Location	Specify the name of the destination S3 bucket or ADLS container you want to write to. For S3, enter a value in the form: `s3a://[*Destination S3 Bucket]` For ADLS, enter a value in the form: `abfs://[Destination ADLS File System]@[Destination ADLS Storage Account*].dfs.core.windows.net`
Google Drive Folder ID	Specify the ID of the Google Drive folder you want to read from.
Google Service Account Key File	Upload the Google Service Account key file in JSON format.
Include Subfolder Files	Specify whether to include a list of files from subfolders. Set to "true" to include files from subfolders Set to "false" to only list files from the specified Google Drive folder. The default value is `true`.