Specifies the behavior of the test connection operation.

Possible Values

READ_FILE, LIST_FILES, NO_OPERATION, AUTHENTICATE, LIST_OR_READ_FILES

Data Type

string

Default Value

"LIST_OR_READ_FILES"

Remarks

Changes how the provider responds to a test connection operation based on the integration scenario.

LIST_OR_READ_FILES

List and read files from the storage source until at least one is parsed. Fails if none of the files can be parsed (are invalid). Succeeds even if the directory contains no SAS Data Sets files since this provider supports creating files. Note: this mode will not read files in sub-directories. This is the most flexible option and works with both directory and file URIs.

READ_FILE

Validates that the URI points to a readable SAS Data Sets file. The URI must point to an existing SAS Data Sets file, not a directory. This behavior will fail if the file does not exist or contains invalid SAS Data Sets content.

LIST_FILES

Validates that the URI points to a directory and lists its contents. Succeeds even if the directory contains no SAS Data Sets files since this provider supports creating files.

NO_OPERATION

Performs basic URI validation without accessing files or verifying their existence. This is useful for quickly validating configuration without network or file system operations.

AUTHENTICATE

Validates connection credentials and URI accessibility. For cloud storage, this verifies authentication. For local files, this checks URI format and basic accessibility.

Notes

• The SAS Data Sets provider behavior depends on the storage type. Local storage supports both read and write operations, while remote storage (cloud storage, FTP, SFTP) is read-only.
• For local file connections, empty or non-existing directories are acceptable for most test behaviors since the driver can create new SAS data sets during write operations.
• For remote storage connections, empty directories will cause failures for LIST_FILES and LIST_OR_READ_FILES behaviors since a read-only connection with no files is unusable.

Behavior by URI examples

Local Storage (file://)

The SAS Data Sets supports both read and write operations for local storage. Empty directories are acceptable since new files can be created.

URI Type	NO_OPERATION	READ_FILE	LIST_FILES	LIST_OR_READ_FILES	AUTHENTICATE
Folder with SAS files	Success	Failure: URI must point to an existing file	Success	Success	Success
Empty folder	Success	Failure: URI must point to an existing file	Success	Success	Success
Non-existing directory	Success	Failure: URI must point to an existing file	Success	Success	Success
Valid SAS file	Success	Success	Failure: URI must point to an existing directory	Success	Success
Non-existing file	Success	Failure: URI must point to an existing file	Failure: URI must point to an existing directory	Failure: URI must point to valid file or directory	Success
Invalid SAS content	Success	Failure: Parsing error	Failure: URI must point to an existing directory	Failure: Parsing error	Success

Remote Storage (S3, Azure, FTP, etc.)

The SAS Data Sets is read-only for cloud storage. Empty directories will cause failures for behaviors that attempt to read files.

URI Type	NO_OPERATION	READ_FILE	LIST_FILES	LIST_OR_READ_FILES	AUTHENTICATE
Folder with SAS files	Success	Failure: URI must point to an existing file	Success	Success	Success
Empty folder	Success	Failure: URI must point to an existing file	Failure: Directory is empty	Failure: Directory is empty	Success
Non-existing directory	Success	Failure: URI must point to an existing file	Success	Success	Success
Valid SAS file	Success	Success	Failure: URI must point to an existing directory	Success	Success
Non-existing file	Success	Failure: URI must point to an existing file	Failure: URI must point to an existing directory	Failure: URI must point to valid file or directory	Success
Invalid SAS content	Success	Failure: Parsing error	Failure: URI must point to an existing directory	Failure: Parsing error	Success
Invalid credentials	Success	Failure: Authentication failed	Failure: Authentication failed	Failure: Authentication failed	Failure: Authentication failed