You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It make sense for user to execute plasmactl update anywhere on system
Including in a directory where no keyring exists, like user home or system root
Expected
To avoid creating keyring files in random place of system, it's probably best not for update command not to have abiltiy to create new keyrings
That way, command will use keyring if it already exists (in most case, project directory) and not polute the system otherwise
So in case keyring not found in ./{binary-name}/keyring.yaml.age of current directory, then prompt user for credentials, to be used right away and not be stored anywhere
The text was updated successfully, but these errors were encountered:
Observed
plasmactl update
anywhere on systemExpected
update
command not to have abiltiy to create new keyrings./{binary-name}/keyring.yaml.age
of current directory, then prompt user for credentials, to be used right away and not be stored anywhereThe text was updated successfully, but these errors were encountered: