naziba321
commented
2 days ago Hi @DustinMoriarty, thank you for raising this!
This connect-sdk-python repo is for interacting with a Connect server, while the onepassword-sdk-python is for interacting directly to 1Password. These are two different SDKs and they are used for different purposes, and they are both currently actively maintained.
The documentation you are looking at is for interacting directly with 1Password and currently this works with service accounts. We also mention the Connect SDK for python in our guide for setting up Connect.
I’ve noticed you mention trying to solve your use case by building a CLI wrapper in Java. While we currently don’t support this language, if you’re currently using Connect, then you might want to check out this community-built Java SDK for Connect.
As for Python SDK, you have the following options:
- connect-sdk-go for managing secrets using 1Password Connect server
- onepassword-sdk-python for managing secrets using a service account
- pyonepassword, a community-built wrapper for CLI if you want to use the functionality of the CLI.
DustinMoriarty
edif2008
Summary
This connect-sdk-python library is not in the list of supported SDK's on the OP Documentation. However, onepasword-connect-python is linked. Onepassword-connect-python is not yet published to PyPi and is not yet at version 1.0.0. This repo, Connect-sdk-python, appears to be more mature than Onepassword-connect-python, yet it is not mentioned. We need clarity about the future support plan for this connect-sdk-python. Right now, there does not appear to be a production ready python SDK for OP that is endorsed by OP in the documentation. We are reluctant to use this SDK because we don't know if OP will continue to support it and we are reluctant to use onepasword-connect-python because it does not appear stable yet.
Use cases
We need to know OP's Python SDK support plan so that we can plan our current and future use of OP SDK's.
Proposed solution
Document the current state of this library and it's support plan in the OP Documentation and in the README.md file of this repo. If this library is planned to stop receiving updates at some point, publish an end of life (EOL) date. Otherwise, state that this library is expected to remain supported for the foreseeable future and also link to this library from the documentation.
Is there a workaround to accomplish this today?
We are currently planning to not use any OP Python SDK. We are currently wrapping the OP CLI with Java instead, which is a fairly ugly solution.
References & Prior Work