Add make registry.json command

[hculea]

Overview

This PR adds a make registry.json command, generating a json-formatted registry.

For the time being, this will be used as configuration for the Shell Plugins banners that OPH renders for Shell Plugins items. However, this can also serve as boilerplate for more complex configuration that can be built on top of this repo.

Type of change

• Created a new plugin
• Improved an existing plugin
• Fixed a bug in an existing plugin
• Improved contributor utilities or experience

How To Test

Run make registry.json

[accraw]

Functional test, check!

Should we add plugins/registry.json to .gitignore?

[accraw]

Do you think it might make sense to include the name of the executable? For example, I would be more likely to name my cred for Oh Dear ohdear and not have the management url.

[arunsathiya]

This looks good to me! A couple of questions for consideration:

• Should we support multiple credentials in the registry? When in the future multiple credentials are supported, we'd want to record separate management URLs for them. One example is ngrok: right now the authtoken and API Key are bundled together as one credential, but it'd be ideal to have them as individual credentials.
• For shell plugins without a management URL, are we directing to the docs page?

[arunsathiya]

Not necessarily questions but some drive-by thought processes:

Multi-executable shell plugins, and shell plugins that depend on other company secrets. Homebrew is an example of the latter, which uses GitHub Personal Access Tokens for authentication.

If we are doing pattern matching based on the platform name, for example, should we show only the GitHub shell plugin (on the banner) on a GitHub secret, or show the Homebrew shell plugin as well?

If we are pattern matching with the URL in the secret item, should we show both GitHub and Homebrew shell plugins in that banner? If we choose to show more than one, will that constraint what we can show within that banner?

[hculea]

Added to .gitignore, thanks @accraw !

Do you think it might make sense to include the name of the executable? For example, I would be more likely to name my cred for Oh Dear ohdear and not have the management url.

I suggest we carry out this discussion on the internal MR where this json gets used, as the PR here lacks context about the current intended consumption mechanism for this json.

[hculea]

Should we support multiple credentials in the registry?

good point! I'll make sure to open an internal ticket about this. 😄

For shell plugins without a management URL, are we directing to the docs page?

https://developer.1password.com/docs/cli/shell-plugins/

[arunsathiya]

Current changes look good to me!

[accraw]

Looks good to me for this iteration, can discuss improvements or other changes internally later.