In Progress
Status Update
Comments
da...@recursion.com <da...@recursion.com> #2
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
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com>
mi...@kognic.com <mi...@kognic.com> #3
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?
li...@google.com <li...@google.com> #4
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:
What I would like to do is use standard tooling like but pointed at our private PyPI server (I plan to fork or contribute to this library to make the url configurable) so we can also scan our internal packages. The problem is this and other tools are meant to work with the public PyPI, so it would be nice if Artifact Registry would provide compatibility with PyPI warehouse's API. Specifically, I'd like to pull package metadata as json from the https://peps.python.org/pep-0691/#project-detail , or using the legacy
libyear
/simple/<project>
endpoint as described here:/json
endpoint.What you expected to happen:
I'd like a good way to be able to read metadata from a PyPI package without needing to download a wheel every time and inspecting that. Ideally, I would want something that works the same way as public PyPI and not utilize custom gcloud commands because doing so makes our solution less compatible with OSS.
Steps to reproduce:
I am going to steal some code from my DoIT rep who was able to reproduce the problem:
Other information (workarounds you have tried, documentation consulted, etc):
My workaround that I have not developed yet, would be to use a combination of downloading a package from Artifact Registry and optionally building a wheel if it is a source distribution and then using to grab dependencies and other metadata for analysis.
wheel-inspect