Assigned
Status Update
Comments
ku...@google.com <ku...@google.com>
ku...@google.com <ku...@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
ky...@wildfire-corp.com <ky...@wildfire-corp.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?
br...@ghost.security <br...@ghost.security> #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.
so...@suki.ai <so...@suki.ai> #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: Support on Artifact Registry for "FROM scratch" [1] docker images.
How this might work: This will avoid the error message "Missing os-release file", as this is not a supported docker image and fails the Artifact Registry Vulnerability Scanning [2].
If applicable, reasons why alternative solutions are not sufficient:
Seeing vulnerabilities in the OS's of the images being used before - these are just single Go binaries which is a perfect fit for scratch images.
Other information (workarounds you have tried, documentation consulted, etc):
[1]
[2]