Edit

Share via

How to use the BlobFuse2 secure set command to change the value of a parameter in an encrypted BlobFuse2 configuration file

  • Article

Use the blobfuse2 secure set command to change the value of a specified parameter in an encrypted BlobFuse2 configuration file.

Syntax

blobfuse2 secure set --[flag-name]=[flag-value]

Flags (options)

Flags that apply to blobfuse2 secure set are inherited from the grandparent command, blobfuse2, or apply only to the blobfuse2 secure subcommands.

Flags inherited from the BlobFuse2 command

The following flags are inherited from grandparent command blobfuse2:

Flag Short version Value type Default value Description
disable-version-check boolean false Enables or disables automatic version checking of the BlobFuse2 binaries
help -h n/a Help info for the blobfuse2 command and subcommands

Flags inherited from the BlobFuse2 secure command

The following flags are inherited from parent command blobfuse2 secure:

Flag Value type Default value Description
config-file string ./config.yaml The path configuration file
output-file string Path and name for the output file
passphrase string The Key to be used for encryption or decryption
Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE.
The key must be 16 (AES-128), 24 (AES-192), or 32 (AES-256) bytes in length.

Flags that apply only to the BlobFuse2 secure set command

The following flags apply only to command blobfuse2 secure set command:

Flag Short
version		 Value
type		 Default
value		 Description
key string Configuration key (parameter) to be updated in an encrypted config file
value string New value for the configuration key (parameter) to be updated in an encrypted config file

Examples

Note

The following examples assume you have already created a configuration file in the current directory.

Set the value of parameter logging.log_level in an encrypted BlobFuse2 configuration file to "log_debug":

blobfuse2 secure set --config-file=config.yaml --passphrase=PASSPHRASE --key=logging.log_level --value=log_debug

See also