Assigned
Status Update
Comments
ma...@leovegas.com <ma...@leovegas.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
ma...@leovegas.com <ma...@leovegas.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?
ep...@gmail.com <ep...@gmail.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.
ch...@priceline.com <ch...@priceline.com> #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)
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Every time the customer's automated process creates a really long name for their Maven Repository snapshots, they receive a “400 Bad Request” error, which needs manual intervention from their side for every time this happens.
Artifact Registry has a system limit on groupId + artifactId <= 256 symbols, which is preventing the customer from using long names for their snapshots.
We want to explore the possibility of increasing this limitation.
How this might work:
Increasing the system limit for Artifact Registry snapshot names would help the processes run normally without the need for manual intervention regardless of the length of the snapshot name.
If applicable, reasons why alternative solutions are not sufficient:
When the snapshot name gets created by automated processes, it makes it difficult for the customers to track the length and avoid reaching the limit.