-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
bugfix - Prevent passwordstore lookup to create subkey when create == false #9106
base: main
Are you sure you want to change the base?
Conversation
… false Fixes#9105
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! I've added a first comment below.
changelogs/fragments/9106-passwordstore-fix-subkey-creation-even-when-create-==-false.yml
Outdated
Show resolved
Hide resolved
CC @mluzarreta |
…en-when-create-==-false.yml Co-authored-by: Felix Fontein <[email protected]>
Suggestions applied @felixfontein |
result.append(self.update_password()) | ||
if self.paramvals["subkey"] != "password" and not self.passdict.get(self.paramvals['subkey']): # password exists but not the subkey | ||
with self.opt_lock('write'): | ||
result.append(self.update_password()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure whether this is correct. Right before the if
, you're already running result.append(self.update_password())
, and now, under a certain condition, you run it a second time.
SUMMARY
Prevent passwordstore lookup to create subkey when create == false
Fixes #9105
ISSUE TYPE
COMPONENT NAME
passwordstore lookup