-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Unauthorized publish/add using keyring with GCP Artifact Registry #4454
Comments
I've been able to get this to work (most of the time) by setting the keyring service poetry looks for when using a 'legacy repository'. First, you have to add the repository to config: then you can set the keyring service for that repository: Note: Really hoping we have an update for this soon. |
Unfortunately, I get the same 401 errors for publish and add using the method you shared, @jaycarroll. Thank you for sharing though. Perhaps I have something additional misconfigured. |
@boweevil Keyring authentication is handled with the following PR #4086 (slated for release with version As for the Let me know if that helps. I am unaware a technique beyond defining two separate repositories for supporting publish and pull on different URLs to the same repository. If you have a solution, I am all ears. |
It looks like this is solved in version 1.2.0a2. So, I agree that |
Closed as #4086 is merged. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
When trying to publish a package to or add a package from a private GCP Artifact Registry using keyring, I get a 401 unauthorized error. I have followed this guide as closely as possible in an attempt to adapt it to the poetry use case. I am able to publish using
twine
and pull usingpip
. In poetry's documentation it talks about supporting keyring. However, it seems this may only be in regards to storing and retrieving username and password. I am prompted for a username only when publishing. I have hit enter at this prompt as I'm trying to use the Google stored credentials in the keyring.Poetry publish
Poetry add
The text was updated successfully, but these errors were encountered: