Currently, we have a parser which parses the input path to ensure valid parameters. In the case of vault paths, the parser check if the path follows the format like vaultName:secretPath. This is not always ideal, as we want to allow specifying the vault's root directory by simply writing vaultName.
This is already partially implemented in the secrets ls command, but this needs to be made a standard. For command which do not operate on directories, like secrets write, this should be another error thrown from within the command, but this shouldn't be an error thrown at the parsing stage.
Specification
Currently, we have a parser which parses the input path to ensure valid parameters. In the case of vault paths, the parser check if the path follows the format like
vaultName:secretPath
. This is not always ideal, as we want to allow specifying the vault's root directory by simply writingvaultName
.This is already partially implemented in the
secrets ls
command, but this needs to be made a standard. For command which do not operate on directories, likesecrets write
, this should be another error thrown from within the command, but this shouldn't be an error thrown at the parsing stage.Additional context
Tasks