Assigned
Status Update
Comments
vo...@google.com <vo...@google.com>
vo...@google.com <vo...@google.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
sa...@hcl.com <sa...@hcl.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?
ny...@google.com <ny...@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.
[Deleted User] <[Deleted User]> #5
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...@logik.io <ja...@logik.io> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
le...@gmail.com <le...@gmail.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
ri...@google.com <ri...@google.com> #8
Comment has been deleted.
ga...@stanley-robotics.com <ga...@stanley-robotics.com> #9
I would like this feature as well.
ol...@gmail.com <ol...@gmail.com> #10
Hello, any progress in here? Please is very frustrating.
gu...@gmail.com <gu...@gmail.com> #11
Hi, open request for more than 3 years for a simple change. Please proceed that.
sa...@gmail.com <sa...@gmail.com> #12
+1. :(
Description
What you would like to accomplish:
The user would like to be able to create directories or folders in a repository.
How this might work:
docker push LOCATION-docker.pkg.dev/PROJECT-ID/default/NAMESPACE//SERVICE/IMAGE:TAG
eg: docker push us-docker.pkg.dev/ss-pp-core-d/default/core/client-service
If applicable, reasons why alternative solutions are not sufficient:
Other information (workarounds you have tried, documentation consulted, etc):
Making use of labels and tags to identify and group related repositories.
[1]https://cloud.google.com/artifact-registry/docs/repositories/label-repos
[2] https://cloud.google.com/artifact-registry/docs/repositories/tag-repos