support 1password as backend (#404)

[hackardoX]

This adds 1Password support!

[hackardoX]

99designs/aws-vault#404

[hackardoX]

Hi @mtibben @lwc @creativej @spearki,
could you please review this when you have time?

[hackardoX]

The unit tests pass locally, however, I am not sure how to make it works in the ci/cd. I am afraid that a 1password account is required

[lugoues]

One option, if the team is willing, is to sign up for a free open source team account and create a test user. https://github.com/1Password/1password-teams-open-source

[hraban]

Maybe someone from AgileBits/1Password can help here? Jack (@plttn ) I hope you don't mind me asking what do you think would be the best way to go about helping the aws-vault team get their 1Password integration unit tests to pass in CI? Do you know the best person to contact?

[plttn]

Hey there! As mentioned, your best bet would be to sign up for our 1Password for Open Source program.

Once you've been approved, you could use a 1Password Service Account in that team account to do your unit tests in Github Actions. If the environment variable OP_SERVICE_ACCOUNT_TOKEN is set in GitHub Actions, 1Password CLI will use that credential when performing actions, which should allow your CI/CD to pass.

Cheers!

[hackardoX]

Any news on this? @lox maybe you can have a look?

[chrisgilmerproj]

Thanks for writing this MR @andrea11 . 1password support would be really great on systems that only have the CLI. I'm currently using pass as the backend but it would be wonderful to switch to 1password where I store everything else. Any chance we could get this merged in, even if its hidden behind some kind of experimental flag?

[AndyTitu]

Also, 1Password now has a Go SDK https://github.com/1Password/onepassword-sdk-go that could make building this easier.

[hackardoX]

Hello everyone,
Thank you, @AndyTitu, for pointing me toward the SDK. While I could potentially implement it, I’d prefer to confirm with a maintainer first to ensure there’s interest in merging this PR. I noticed that the last merged commit in this repository dates back about three years. Do you know if it’s still actively maintained? (cf. #138)

[mbevc1]

We have PR opened in the maintained fork: ByteNess#26

Thanks to @manselmi 🚀