gopass: Make NAMESPACE customizable

[stefanmore]

Hi,
First of all, thank you for all your efforts in creating the gopass helper / this fork!

Context:

I noticed that currently NAMESPACE is hardcoded to io.container.registries, i.e., passwords are stored in ~/.password-store/io.container.registries.

For some reason, another machine I used to use put passwords into the docker-credential-helpers namespace. Unfortunately, I cannot remember which helper I used at the time.

Feature Proposal:

Thus, I propose to allow the customization of NAMESPACE, e.g., via ~/.docker/config.json.

Obviously, there are workarounds (such as moving the old passwords or modifying the variable before compiling). So this is not a high-proprity PR.

[stefanmore]

I just noticed that the pass helper uses the docker-credential-helpers string:

docker-credential-helpers/pass/pass.go

Line 24 in 9082d90

const PASS_FOLDER = "docker-credential-helpers" //nolint:revive

Perhaps I used a wrapper around 'pass' in the past ...

[sudoforge]

Note

i apologize for the delayed response. apparently i never enabled notifications for this fork. or maybe i had explicitly disabled them after creating it. regardless, i've enabled them now.

---

this sounds resonable to me. it looks like i have some conflicts to sort out before i can rebase against upstream, but i'll take care of that in the next few days.

regarding this feature request: being able to customize the namespace sounds reasonable to me. i'd rather not read from another program's file, because that isn't guaranteed to exist (e.g. i don't use docker and thus do not have a ~/.docker dir), so we'd either need to conditionally read from a bunch of different files, support a CLI flag (which may or may not fit in with upstream's designs), read from an environment variable, or support configuration through a custom file.

of those options, the last sounds best to me.

that said... i had initially planned to build an independent credential helper, because it looked like (at the time) upstream had been stagnating for a while. i never got too far with building it, but, i'd still consider doing that so that gopass has first-class support for integrating with container tooling.