Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for op version 2 ? #64

Open
sdahlbac opened this issue Mar 21, 2022 · 5 comments
Open

Support for op version 2 ? #64

sdahlbac opened this issue Mar 21, 2022 · 5 comments
Assignees
Labels
enhancement New feature or request

Comments

@sdahlbac
Copy link
Contributor

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Op version 2 seems to have changed the commandline arguments.

https://developer.1password.com/docs/cli/upgrade/

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@sdahlbac sdahlbac added the enhancement New feature or request label Mar 21, 2022
@anasinnyk
Copy link
Owner

Hi @sdahlbac I think we can use API for that. When I started this project 1Password didn't have API. But I don't have any time for implement that. Sorry.

@sdahlbac
Copy link
Contributor Author

You mean the one needing secrets automation? If so, then I presume the official 1password provider is the way to go?

Based on the docs of op version 2 (specifically the bit about the binary having to be called exactly /usr/local/bin/op) I thought that this provider using op v1 would block cli usage of op v2. However, it does not seem to be that black and white. Op v2 runs fine even called op2, but possibly auto updates might not work?

@anasinnyk
Copy link
Owner

anasinnyk commented Apr 19, 2022

Yes I think better way uses this official provider https://registry.terraform.io/providers/1Password/onepassword

@stopthatastronaut
Copy link

Ah, I assume this is why I'm getting

Error: Cannot signin: [ERROR] 2022/09/21 10:01:53 unknown flag: --output

@sdahlbac
Copy link
Contributor Author

As a simpler solution, could we first check eg. /usr/local/bin/op1 and use that if it exists. That way one could have the new op v2 installed in the expected location and this provider could still work with op version 1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants