Skip to content

Project-level Provider Aliases #57

@theutz

Description

@theutz

I'm not sure if I'm missing something here or not, but it seems like it'd make sense to be able to set provider aliases at the project level. Since these values end up hard-coded into the repo, it seems like their definition should exist in the same place.

I'm aware that I could write commands to imperatively setup these aliases for each user, but I see a few drawbacks to that approach:

  1. An extra setup step is required
  2. If a user is working on multiple projects, there could be namespace issues with vaults, etc.
  3. The value for the provider feels like a "magic string"

Ideally, it'd be great to have something like this:

[defaults]
provider = "onepassword://Account@Vault"

OR, alternatively this:

[provider_aliases]
1p = "onepassword://Account@Vault"

[profile.default.defaults]
provider = "1p"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions