Downloads the changes to the server based on modifications to a local copy of the keyboard description which will update the maps for one or more indicators
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --aws-await-snapshots-timeout The length of time in seconds to wait for snapshots to be created in AWS before timing out (default: 3600 seconds). --aws-snapshot-lock-mode The lock mode for the snapshot. This is only valid if --snapshot-instance and --snapshot-disk are set. Allowed options: 7.0 (bu 2 compliance. (bu 2 governance. --aws-snapshot-lock-duration The lock duration is the period of time (in days) for which the snapshot is to remain locked, ranging from 1 to 36,500. Set either the lock duration or the expiration date (not both). --aws-snapshot-lock-cool-off-period The cooling-off period is an optional period of time (in hours) that you can specify when you lock a snapshot in compliance mode, ranging from 1 to 72. --aws-snapshot-lock-expiration-date The lock duration is determined by an expiration date in the future. It must be at least 1 day after the snapshot creation date and time, using the format YYYY-MM-DDTHH:MM:SS.sssZ. Set either the lock duration or the expiration date (not both). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --azure-subscription-id The ID of the Azure subscription which owns the instance and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-project GCP project under which disk snapshots should be stored. --snapshot-gcp-project (deprecated) GCP project under which disk snapshots should be stored - replaced by --gcp-project. --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS. --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-zone (deprecated) Zone of the disks from which snapshots should be taken - replaced by --gcp-zone
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --addressing-style The S3 addressing style to use when connecting to S3-compatible cloud storage. This option is useful when using custom S3 endpoints (such as MinIO) that may require a specific addressing style. Allowed options: 7.0 (bu 2 auto (default): Uses the addressing style determined by the boto3 library. (bu 2 virtual: Uses virtual-hosted-style addressing (bucket-name.s3.amazonaws.com). (bu 2 path: Uses path-style addressing (s3.amazonaws.com/bucket-name). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). --aws-region The name of the AWS region containing the EC2 VM and storage volumes defined by the --snapshot-instance and --snapshot-disk arguments. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --azure-resource-group The name of the Azure resource group to which the compute instance and disks defined by the --snapshot-instance and --snapshot-disk arguments belong. Extra options for GCP cloud provider 0.0 --gcp-zone Zone of the disks from which snapshots should be taken. --snapshot-recovery-zone (deprecated) Zone containing the instance and disks for the snapshot recovery - replaced by --gcp-zone
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). -e / --encryption The encryption algorithm used when storing the uploaded data in S3. Allowed options: 7.0 (bu 2 AES256. (bu 2 aws:kms. --sse-kms-key-id The AWS KMS key ID that should be used for encrypting the uploaded data in S3. Can be specified using the key ID on its own or using the full ARN for the key. Only allowed if -e / --encryption is set to aws:kms. Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default. --encryption-scope The name of an encryption scope defined in the Azure Blob Storage service which is to be used to encrypt the data in Azure. --max-block-size The chunk size to be used when uploading an object via the concurrent chunk method (default: 4MB). --max-concurrency The maximum number of chunks to be uploaded concurrently (default: 1). --max-single-put-size Maximum size for which the Azure client will upload an object in a single request (default: 64MB). If this is set lower than the Postgres WAL segment size after any applied compression then the concurrent chunk upload method for WAL archiving will be used. Extra options for GCP cloud provider 0.0 --kms-key-name The name of the GCP KMS key which should be used for encrypting the uploaded data in GCS
replaced by --aws-profile. --read-timeout The time in seconds until a timeout is raised when waiting to read from a connection (defaults to 60 seconds). Extra options for the Azure cloud provider 0.0 --azure-credential / --credential Optionally specify the type of credential to use when authenticating with Azure. If omitted then Azure Blob Storage credentials will be obtained from the environment and the default Azure authentication flow will be used for authenticating with all other Azure services. If no credentials can be found in the environment then the default Azure authentication flow will also be used for Azure Blob Storage. Allowed options are: 7.0 (bu 2 azure-cli. (bu 2 managed-identity. (bu 2 default
beets configuration file Beets has an extensive configuration system that lets you customize nearly every aspect of its operation. To configure beets, you create a file called config.yaml. The location of the file depends on your platform (type beet config -p to see the path on your system): 0.0 (bu 2 On Unix-like OSes, write ~/.config/beets/config.yaml. (bu 2 On Windows, use %APPDATA%ebeetseconfig.yaml. This is usually in a directory like C:eUserseYoueAppDataeRoaming. (bu 2 On OS X, you can use either the Unix location or ~/Library/Application Support/beets/config.yaml. You can launch your text editor to create or update your configuration by typing beet config -e. (See the %config command for details.) It is also possible to customize the location of the configuration file and even use multiple layers of configuration. See %Configuration Location, below. The config file uses X'tty: link https://yaml.org/'%YAMLX'tty: link' syntax. You can use the full power of YAML, but most configuration options are simple key/value pairs. This means your config file will look like this: 0.0 3.5 C option: value another_option: foo bigger_option: key: value foo: bar P In YAML, you will need to use spaces (not tabs!) to indent some lines. If you have questions about more sophisticated syntax, take a look at the X'tty: link https://yaml.org/'%YAMLX'tty: link' documentation. The rest of this page enumerates the dizzying litany of configuration options available in beets. You might also want to see an %example. 0.0 (bu 2 %Global Options 2.0 (bu 2 %library (bu 2 %directory (bu 2 %plugins (bu 2 %include (bu 2 %pluginpath (bu 2 %ignore (bu 2 %ignore_hidden (bu 2 %replace (bu 2 %path_sep_replace (bu 2 %asciify_paths (bu 2 %art_filename (bu 2 %threaded (bu 2 %format_item (bu 2 %format_album (bu 2 %sort_item (bu 2 %sort_album (bu 2 %sort_case_insensitive (bu 2 %original_date (bu 2 %overwrite_null (bu 2 %artist_credit (bu 2 %per_disc_numbering (bu 2 %aunique (bu 2 %sunique (bu 2 %terminal_encoding (bu 2 %clutter (bu 2 %max_filename_length (bu 2 %id3v23 (bu 2 %va_name (bu 2 %UI Options 2.0 (bu 2 %color (bu 2 %colors (bu 2 %terminal_width (bu 2 %length_diff_thresh (bu 2 %import (bu 2 %Importer Options 2.0 (bu 2 %write (bu 2 %copy (bu 2 %move (bu 2 %link (bu 2 %hardlink (bu 2 %reflink (bu 2 %resume (bu 2 %incremental (bu 2 %incremental_skip_later (bu 2 %from_scratch (bu 2 %quiet (bu 2 %quiet_fallback (bu 2 %none_rec_action (bu 2 %timid (bu 2 %log (bu 2 %default_action (bu 2 %languages (bu 2 %ignored_alias_types (bu 2 %detail (bu 2 %group_albums (bu 2 %autotag (bu 2 %duplicate_keys (bu 2 %duplicate_action (bu 2 %duplicate_verbose_prompt (bu 2 %bell (bu 2 %set_fields (bu 2 %singleton_album_disambig (bu 2 %Autotagger Matching Options 2.0 (bu 2 %max_rec (bu 2 %preferred (bu 2 %ignored (bu 2 %required (bu 2 %ignored_media (bu 2 %ignore_data_tracks (bu 2 %ignore_video_tracks (bu 2 %Path Format Configuration (bu 2 %Configuration Location 2.0 (bu 2 %Environment Variable (bu 2 %Command-Line Option (bu 2 %Default Location (bu 2 %Example
Polling and wait set operations fi_poll_open / fi_close Open/close a polling set fi_poll_add / fi_poll_del Add/remove a completion queue or counter to/from a poll set. fi_poll Poll for progress and events across multiple completion queues and counters. fi_wait_open / fi_close Open/close a wait set fi_wait Waits for one or more wait objects in a set to be signaled. fi_trywait Indicate when it is safe to block on wait objects using native OS calls. fi_control Control wait set operation or attributes
The principal handing functions. A Kerberos principal is a email address looking string that contains two parts separated by . The second part is the kerberos realm the principal belongs to and the first is a list of 0 or more components. For example lha@SU.SE host/hummel.it.su.se@SU.SE host/admin@H5L.ORG See the library functions here: Heimdal Kerberos 5 principal functions