Signiant Flight CLI allows you to assign storage to your account to simplify the credentials used to transfer files to and from your cloud storage. You can also create configuration files to reduce the amount of arguments entered on the command line to transfer files easier.
You can also generate log files in standard and batch-mode format to keep track of transfer activity, as well as troubleshoot any errors that you may encounter when transferring files to and from cloud storage.
By assigning storage through the Flight Console, you can simplify your credential requirements for uploading and downloading to a cloud storage object, as well as improve your organizational security by restricting access to a defined Azure container or AWS bucket. Instead of using your secure AWS or Azure credentials, assigned storage is identified by a Config ID, which acts as a secure token, allowing Flight to transfer files to and from your bucket or container.
To assign storage to your account:
Once you assign your cloud storage to your account, you can use the Config ID to securely transfer files to and from storage.
./sigcli --direction upload \ example-video-file.mp4 \ --apikey ABC123456XYZ \ --server us-east-az.cloud.signiant.com \ --configid ABC123456XYZ \
Note: Command examples use
\ to clarify separate parameters. You can also enter commands as a single line. All sensitive credentials in the example are substitued for
A configuration file allows you to set parameters such as user credentials and storage destinations so that your users do not need to retype parameters for each transfer. Any setting in the configuration file can be overridden by using command line parameters.
By default, all distributions of Flight CLI include a
config.cfg file for use with the Flight CLI free trial. When you are ready to use Flight CLI in your organization edit the
config.cfg file in your Flight CLI directory.
The configuration includes parameters to store values for your API key, Flight Server URL, storage credentials or storage config ID, transfer direction, and bucket or container.
Once you finished editing your
config.cfg file, Flight CLI will automatically use the settings contained in that file.
You can define multiple configuration files for different scenarios using the
./sigcli --direction upload \ example-video-file.mp4 \ --config-file alternate_config.cfg
Note: If your users are uploading to more than one AWS S3 Bucket or Azure Blob Container, you can omit the storage location from your configuration file and have users enter the bucket name via the command line.
When moving content, you can specify paths to source and destination files. You can specify a path to a target file, as well as a subdirectory on your cloud storage service.
./sigcli --direction upload \ ~/example-source-directory/example-video-file.mp4 \ /example-target-directory/example-video-file.mp4
You can save logging output to a file by using the
--log-file option and specifying a log file to create with the log data.
./sigcli --direction upload \ example-video-file.mp4 \ --log-file transfer-log.txt
To generate a standardized log output, you can enable the
--batch-mode option to create a log file that uses RFC822-like headers and content to record information.
Note: Log files are over-written whenever you output logs of more than one transfer to the same log file