Skip to content

Update blobfuse2-commands-secure-set.md #124840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update blobfuse2-commands-secure-set.md #124840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions articles/storage/blobs/blobfuse2-commands-secure-set.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ ms.author: akashdubey

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

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

## Syntax

Expand All @@ -36,18 +36,18 @@ The following flags are inherited from parent command [`blobfuse2 secure`](blobf

| 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<br />Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE.<br />The key must be 16 (AES-128), 24 (AES-192), or 32 (AES-256) bytes in length. |
| config-file | string | ./config.yaml | The path of the encrypted configuration file |
| output-file | string | | The path and name for the output file |
| passphrase | string | | The key to be used for encryption or decryption<br />Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE.<br />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<br />version | Value<br />type | Default<br />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 |
| key | | string | | The configuration key (parameter) to be updated in an encrypted configuration file |
| value | | string | | The new value for the configuration key (parameter) to be updated in an encrypted configuration file |

## Examples

Expand All @@ -56,7 +56,7 @@ The following flags apply only to command `blobfuse2 secure set` command:

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`
`blobfuse2 secure set --config-file=./config.yaml --passphrase=PASSPHRASESAMPLE --key=logging.log_level --value=log_debug`

## See also

Expand Down