-
Notifications
You must be signed in to change notification settings - Fork 1
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
feature request: run the script unsupervised #1
Comments
Hi, Thanks for the feedback. I've pushed an update which will allow you to specify the password in the environment variable I tried creating two entries with the same name but the script does not throw an error. Could you send me a screenshot of the error you're getting? Please feel free to send a PR if that's easier for you. OS: Debian Buster Regards, |
Hi, Some more insights : it appears to only occur if both the name of the entry and the usernames are identical. So it is possibly a relatively rare use care. Still it might be more interesting to output a kdbxfile without the conflicting entries (and showing a warning or error) than no file at all. Or possibly let the user choose the behaviour with e.g. a --fail-on-error=true/false flag or similar. I'll leave it up to you to see if and how you want to handle this. For my part, I renamed the conflicting entries so no problem anymore. |
Hi vojeroen, Thank you for taking the time to look into this. I like your idea of resolving the conflict by appending a sequential suffix like "copy 1". I'll implement it sometime this week. Regards, |
I've released v0.1.3 which adds a suffix like “<name> (1)” to the title for duplicate entries. |
I'll give it a go, thanks! |
Hi,
I'm looking to set up a daily export from Bitwarden to a kdbx file, for which your scripts seems to be good tool. However, for the daily job I have in mind, there are a few modifications required. I'd like to check with you how you prefer this: (a) I can fork your repo and just do my modifications, you don't need to be bothered by it; (b) I can send you a PR with some modifications; (c) I can let you know my feature request and you have a look.
This are the modifications I'm thinking about:
Kind regards,
The text was updated successfully, but these errors were encountered: