Simplify master password requesting about borg-backup

[rgaudin]

Can you elaborate more on this? What's master password requesting and what does Slack have to do with it?

My understanding is that you would like to not input the master password when you create a new repo and instead set up a Slack App that would ask you on Slack so you just have to click a button. Is that it?

If so, then this issue's title is misleading as you want a new slack-integration feature. This would obviously be optional.

I fail to see how this can be worth the effort. In the documented workflow, usage of the master password should be quite rare. Doing this would require writing, maintaining and deploying (and keeping running) a new tool for this sole purpose, with the additional worry that this would hold access to your master bitwarden account.

[kelson42]

Operations requesting the master password are not that rare, in particular with #57.

For now each time this is needed we have to run the Docker container with a dedicated mode and from someone having this password. This is clear and properly documented but cumbersome because it cuts any effort needed this in two clearly different operations and these two operations (in our case) have to be run by two different users.

The workflow I propose is that each time needed the backup system contacts the master user via Slack to enter the master password. That way:

• The flows don't have to be splitted in two, it is only one flow which is waiting the master password
• This is far less cumbersome for the master user (and the backup responsible)
• Assuming the Slack channel is secure, we don't loose in security

There is as well a bit of meta level, where I believe we could use such approach to solve a few tasks which are at the same time hard to fully automatize but recurring enough that this is quite time consuming to do that manually.