Assigned
Status Update
No update yet.
Comments
su...@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
mi...@cellpointmobile.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?
st...@takulabs.io
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.
de...@petsathome.co.uk
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
ja...@unity3d.com
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
mi...@nevercode.io
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
Description
Problem you have encountered:
Within the Artifact Registry>>Under the Repository Name>>Under the Image name are listed the image digests with their respective "Tags". There is a field "Description" which does not get populated neither while creation of repository nor can it be edited/updated post Registry creation. This field remains empty.
What you expected to happen:
The expectation is that Description of the docker images/digest should be populated while creation & have individual edit/update options via console or cloud shell via some update command.
Steps to reproduce:
-Create a Docker repository within the Artifact Registry.
-Obtain an image in it such that it can be pushed & pulled to the Artifact Registry.
-Check the image digest Description field.
Other information (workarounds you have tried, documentation consulted, etc):
-Use tagging as a workaround to manage images