Assigned
Status Update
No update yet.
Comments
ri...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
to...@braincorp.com
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
ri...@google.com
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
Description
This will create a public issue which anybody can view and comment on.
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
I am facing issues with the Artifact Registry, specifically challenges related to slow dependency resolution for Python packages when using the Artifact Registry (AR), and also I need to yank packages from AR.
What you expected to happen:
I am using Poetry (https://github.com/python-poetry/poetry ) to install Python packages. I have one Python Artifact Registry for the internal packages, and another which is a partial mirror of PyPI containing only package versions. I want to install various combinations of packages from both Artifact Registry repositories which turns out to be slow because Poetry will download packages when it cannot get metadata from the API. Therefore, If Artifact Registry implemented PEP 658 or the Warehouse API, similar to the request in
Secondly, I want to yank python packages in the Artifact Registry. I upload packages to the Artifact Registry using "twine". Twine has no way to set Yanked status, and Artifact Registry does not report Yanked status anyway, since it implements only PEP 503.”
Therefore, I would like to have an API to set a package version's Yanked flag true or false and Artifact Registry to implement PEP 592 and PEP 658 features.
Other information (workarounds you have tried, documentation consulted, etc):
I would request you to kindly implement the yanking (PEP 592) and PEP 658 features for Artifact registry.