👋 Welcome everyone! Today we’re stoked to announce our first early access for 1Password’s CLI 2.0! We have spent the last 6 months taking the time to reimagine the future of the CLI for administrators and developers using this tool and we can’t wait to have you test what we’ve been working on. Housekeeping: Please keep in mind that this is an early access so your feedback and insights are crucial to helping us perfect this new version of the CLI. We're user-feedback driven and your questions, comments and advice will help us shape a final version that impacts your daily workflows and makes your day-to-day easier. On the Forum, feel free to create threads anytime you have a question, concern or just product feedback that you’d like to share. You’ll find your fellow testers and 1Password engineers will join in! Our Product and Engineering teams will also be active within this private forum to 1) answer any questions you have and 2) most importantly - listen to your thoughts! We can’t do this without your feedback so please share any and all comments with us as we continue to push more features to address the feedback you give us. Thank you in advance for helping us! What’s New in the 1Password CLI v2. Here are a few of the features that you’ll see in the CLI 2.0 (now or in the upcoming months): Brand NEW v2 Schema: In this new version, we’ve made a number of changes to the way you’ll interact with the CLI. Among those improvements, we’ve switched to a noun-verb command schema (that groups commands by topic rather than operation), changed the JSON output schema to contain more useful information for you, added a human friendly (tabular) output schema, improved and extended the stdin processing so you can chain more commands together and changed positional arguments to flags. We are excited to hear your feedback on how these new changes help you with discovering commands and utilizing our CLI more. Secrets Provisioning: To help developers with provisioning secrets locally (both in pipelines and in production), we’ve also added functionality to the CLI that allows you to load secrets directly from 1Password in environment variables and configuration files. With Secrets Provisioning, you can replace your plaintext secrets with references to the secrets stored in 1Password and load them at runtime of your scripts, applications and other workflows. [COMING SOON] Easier installation via package managers: In our mission to make the CLI 2.0 more accessible, we are working on making it easier to install on developer machines and in your cloud infrastructure by integrating with popular installers like yum, apt and apk. If you have a particular request for these installers be sure to start a thread in this forum! [COMING SOON] Biometric system authentication: We are thrilled to announce that you’ll soon be able to authenticate your 1Password account within the CLI using your fingerprint. Just like we have with our browser extension, we’re bringing the same integration to the CLI 2.0 that you’ve come to trust and love. How to get started: To begin, know that the 2.0 version of the CLI can be run in tandem with the current version. However, we do recommend migrating to our new release so that you can fully test out any scripts and automations that you currently have set up for v1 (and give us feedback on that process). Below you’ll find the following guides for set up, migration and reference commands: https://developer.1password.com/ As another note, we’ll be releasing some fun perks for those of you testing out the CLI 2.0 as a thank you for giving us amazing feedback to help make this launch extraordinary. Stay tuned to the forum and we’ll announce that in a bit! Happy testing!

A

Anonymous

Question

1Password CLI 2.0 Early Access 🥳

Forum|Forum|4 years ago
November 30, 2021
10 replies
469 views

👋 Welcome everyone!

Today we’re stoked to announce our first early access for 1Password’s CLI 2.0!

We have spent the last 6 months taking the time to reimagine the future of the CLI for administrators and developers using this tool and we can’t wait to have you test what we’ve been working on.

Housekeeping: Please keep in mind that this is an early access so your feedback and insights are crucial to helping us perfect this new version of the CLI. We're user-feedback driven and your questions, comments and advice will help us shape a final version that impacts your daily workflows and makes your day-to-day easier.

On the Forum, feel free to create threads anytime you have a question, concern or just product feedback that you’d like to share. You’ll find your fellow testers and 1Password engineers will join in!

Our Product and Engineering teams will also be active within this private forum to 1) answer any questions you have and 2) most importantly - listen to your thoughts! We can’t do this without your feedback so please share any and all comments with us as we continue to push more features to address the feedback you give us. Thank you in advance for helping us!

What’s New in the 1Password CLI v2.

Here are a few of the features that you’ll see in the CLI 2.0 (now or in the upcoming months):

Brand NEW v2 Schema: In this new version, we’ve made a number of changes to the way you’ll interact with the CLI. Among those improvements, we’ve switched to a noun-verb command schema (that groups commands by topic rather than operation), changed the JSON output schema to contain more useful information for you, added a human friendly (tabular) output schema, improved and extended the stdin processing so you can chain more commands together and changed positional arguments to flags. We are excited to hear your feedback on how these new changes help you with discovering commands and utilizing our CLI more.
Secrets Provisioning: To help developers with provisioning secrets locally (both in pipelines and in production), we’ve also added functionality to the CLI that allows you to load secrets directly from 1Password in environment variables and configuration files. With Secrets Provisioning, you can replace your plaintext secrets with references to the secrets stored in 1Password and load them at runtime of your scripts, applications and other workflows.
[COMING SOON] Easier installation via package managers: In our mission to make the CLI 2.0 more accessible, we are working on making it easier to install on developer machines and in your cloud infrastructure by integrating with popular installers like yum, apt and apk. If you have a particular request for these installers be sure to start a thread in this forum!
[COMING SOON] Biometric system authentication: We are thrilled to announce that you’ll soon be able to authenticate your 1Password account within the CLI using your fingerprint. Just like we have with our browser extension, we’re bringing the same integration to the CLI 2.0 that you’ve come to trust and love.

How to get started:

To begin, know that the 2.0 version of the CLI can be run in tandem with the current version. However, we do recommend migrating to our new release so that you can fully test out any scripts and automations that you currently have set up for v1 (and give us feedback on that process). Below you’ll find the following guides for set up, migration and reference commands:

https://developer.1password.com/

As another note, we’ll be releasing some fun perks for those of you testing out the CLI 2.0 as a thank you for giving us amazing feedback to help make this launch extraordinary. Stay tuned to the forum and we’ll announce that in a bit!

Happy testing!

CLI

1

1P_Simon

1Password Employee

Hi and welcome everyone! 👋

I'm excited to learn more about how you're all using the CLI, how we can improve the experience of what you're already doing today and what you'd like to see us add so that you can do even more with the CLI. Your input will help shape the future of 1Password CLI 2.0 and I really appreciate you all joining us on this journey! 🙏

We're here to listen, learn and improve, so any input you have is very welcome! I hope we'll have a ton of engaging conversations and I encourage to https://1password.community/categories/cli-beta and https://1password.community/post/discussion/cli-beta.

Cheers,
Simon
Tech Lead CLI 2.0

artooro

One use-case is using the CLI for SSH credentials. I don't see this talked about in the post above or in the documentation. Is this still coming at some point?

1

1P_Simon

1Password Employee

Yes, we're still working on SSH support.

We'll launch it in a separate Early Access when it's ready. If you've ticked the SSH checkbox https://docs.google.com/forms/d/e/1FAIpQLSelPzb5hnT7nmTnSZIpKXgi4SLMsOk6zeTwix8HQB34__0h7A/viewform, you'll get an email as soon as SSH support is ready for you to give a spin. Thank you for your interest!

A

Anonymous

Thanks for including me in the early access!

I'm finding the "inject" command particularly useful, and I had one question/suggestion about this command. When writing the "reference format" string, is there any way to specify sections/fields with spaces in the names?

For instance, I'm trying to write a reference string for the "api key" field within the "API KEYS" section of my item names "Twitter", and the closest I can get is the following:

op://Personal/Twitter/API_KEYS/api_key

Seeing this docs page mentions that the https://developer.1password.com/docs/cli/reference/commands/inject#:%7E:text=The%20reference%20names%20cannot%20contain%20any%20whitespaces%20or%20special%20characters%2C%20with%20the%20exception%20of%20hyphens%20(%2D)%20and%20underscores%20(_).. However, a lot of my custom sections/fields have spaces in their names. If possible, I would really like to avoid going back and editing them all to use "-" or "_" instead.

Perhaps there could be a way to specify a UUID for the specific section/field instead of inputting the name (assuming such a UUID exists under the hood)? I have already been using the item UUID in the reference string when I have duplicate item names within the same vault, and I've found this alternative very useful.

Thanks in advance, and apologies if I've missed a docs page that explains everything...

A

Anonymous

@dynamitenate check out https://1password.community/discussion/126438/2-3-4-6-spaces-in-secrets-references for the same request :)
UUIDs are already supported (but missing from docs), and spaces hopefully coming.

XIII

What are the numbers in each title?

Should we use those when posting a new topic, or do 1Password employees add them (later)?

1

1P_Simon

1Password Employee

@XIII You can start new threads without the number added. 1Password employees will add these numbers later for internal tracking. We use them to follow up in the thread when we've released changes based on your feedback or when we have any follow up questions.

XIII

Thanks for explaining.

(Initially I saw a few and thought a single poster was doing this for her/his posts, but later almost all had them...)

XIII

Congratulations on releasing this functionality! 🎉

https://blog.1password.com/1password-cli-2.0/

A

Anonymous

@XIII Appreciate your kind words! We hope you continue providing feedback in the main CLI board!

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded