Support for internal/private tools

[shyim]

Platform or tool

Generic

Relevant links

Goal or desired behavior

When you built in your Company a custom tool and don't want to contribute it to this repo. It would make sense to have a basic generic plugin.

So my idea would be to have in the .config folder a yaml file something like

.config/1password/tools/my_comany.yml

executeables:
 - my-company
 mapping:
    MY_SECRET_ENV: field.APIToken
locator:
    DOMAIN: fooo

Deploying these build go files is annoying for Companies. Also break when the SDK moves forward. I have to re-build my plugins from last week :)

Contribution

• I'd be up for building the plugin myself.

Additional information

No response

[SimonBarendse]

Hi @shyim, thank you for opening this feature request!

We'll be evaluating what to do with support for internal tools. We might add support for private plugins separate from the registry in this repository. Maybe private registry/repository as well.

For now, the Shell Plugins feature and this repository are both intended to be used for public tools and services only.