Artifact Registry - Add support for NuGet packages (.NET) [180810242]

Assigned

Feature Request

Status Update

No update yet.

Description

ol...@emz-hanauer.com

created issue #1

Feb 22, 2021 10:09AM

Add NuGet package support for the Artifact registry, so .NET developers can use it to upload and reuse compiled .NET code.

Comments

ts...@google.com <ts...@google.com> #2Mar 24, 2021 05:08PM

Assigned to gc...@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

da...@appgr8.com <da...@appgr8.com> #3May 25, 2021 10:05AM

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?

[Deleted User] <[Deleted User]> #4Sep 20, 2021 02:35PM

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.

cr...@gmail.com <cr...@gmail.com> #5Jun 23, 2022 03:06PM

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)

[Deleted User] <[Deleted User]> #6Jun 27, 2022 12:40AM

Over 3 years to get something as basic as renaming a static IP address. Any progress here?

gs...@mandmdirect.com <gs...@mandmdirect.com> #7Nov 7, 2022 10:50AM

Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!

ry...@gmail.com <ry...@gmail.com> #8Nov 24, 2022 06:04PM

Any progress in here?

ma...@cm.com <ma...@cm.com> #9Jan 4, 2023 03:26PM

I would like this feature as well.

al...@itg.co.uk <al...@itg.co.uk> #10Jan 18, 2023 06:52AM

Hello, any progress in here? Please is very frustrating.

mi...@transactionwarehouse.net <mi...@transactionwarehouse.net> #11Feb 2, 2023 09:52PM

Hi, open request for more than 3 years for a simple change. Please proceed that.

ku...@google.com <ku...@google.com> Feb 3, 2023 08:34AM

Reassigned to ku...@google.com.

ku...@google.com <ku...@google.com> #12Feb 3, 2023 03:09PM

Reassigned to gc...@google.com.

+1. :(

g....@saltosystems.com <g....@saltosystems.com> #13Mar 13, 2023 06:48PM

We need this.

va...@google.com <va...@google.com> Jul 3, 2023 09:07AM

Reassigned to su...@google.com.

su...@google.com <su...@google.com> Jul 4, 2023 02:40PM

Reassigned to gc...@google.com.

gp...@travix.com <gp...@travix.com> #14Jul 26, 2023 02:41PM

please add this!

jr...@bgrove.com <jr...@bgrove.com> #15Jul 26, 2023 02:45PM

+1 !

gp...@travix.com <gp...@travix.com> #16Jul 27, 2023 11:53AM

[Deleted User] <[Deleted User]> #17Jul 31, 2023 12:15AM

ri...@focus-bc.com <ri...@focus-bc.com> #18Aug 4, 2023 10:53PM

We need this please

ni...@unifiedpost.com <ni...@unifiedpost.com> #19Aug 25, 2023 08:26AM

cr...@tokinomo.com <cr...@tokinomo.com> #20Oct 4, 2023 07:44AM

+1

2018 =(

pi...@extendaretail.com <pi...@extendaretail.com> #21Oct 25, 2023 11:39AM

it...@gcp.education.gov.il <it...@gcp.education.gov.il> #22Dec 10, 2023 12:50PM

la...@rome2rio.com <la...@rome2rio.com> #23Dec 20, 2023 02:55AM

de...@gmail.com <de...@gmail.com> #24Jan 2, 2024 04:38PM

in...@traceable.ai <in...@traceable.ai> #25Jan 30, 2024 06:33PM

+1 (again) coming up to 5 years?

ri...@google.com <ri...@google.com> #26Mar 4, 2024 07:45PM

ba...@google.com <ba...@google.com> May 21, 2024 11:06AM

Reassigned to ku...@google.com.

ku...@google.com <ku...@google.com> May 30, 2024 01:23PM

Reassigned to gc...@google.com.

el...@gmail.com <el...@gmail.com> #27Jun 11, 2024 01:22PM

se...@gmail.com <se...@gmail.com> #28Aug 26, 2024 02:34PM

ta...@google.com <ta...@google.com> #29Sep 5, 2024 08:45AM

Ru...@tbint.de <Ru...@tbint.de> #30Oct 24, 2024 11:35AM

el...@gmail.com <el...@gmail.com> #31Oct 24, 2024 01:20PM

ri...@google.com <ri...@google.com> #32Jan 9, 2025 07:05PM

Reassigned to ri...@google.com.

Issue 180810242

Description

Issue summary

Comments

ts...@google.com <ts...@google.com> #2Mar 24, 2021 05:08PM

da...@appgr8.com <da...@appgr8.com> #3May 25, 2021 10:05AM

[Deleted User] <[Deleted User]> #4Sep 20, 2021 02:35PM

cr...@gmail.com <cr...@gmail.com> #5Jun 23, 2022 03:06PM

[Deleted User] <[Deleted User]> #6Jun 27, 2022 12:40AM

gs...@mandmdirect.com <gs...@mandmdirect.com> #7Nov 7, 2022 10:50AM

ry...@gmail.com <ry...@gmail.com> #8Nov 24, 2022 06:04PM

ma...@cm.com <ma...@cm.com> #9Jan 4, 2023 03:26PM

al...@itg.co.uk <al...@itg.co.uk> #10Jan 18, 2023 06:52AM

mi...@transactionwarehouse.net <mi...@transactionwarehouse.net> #11Feb 2, 2023 09:52PM

ku...@google.com <ku...@google.com> Feb 3, 2023 08:34AM

ku...@google.com <ku...@google.com> #12Feb 3, 2023 03:09PM

g....@saltosystems.com <g....@saltosystems.com> #13Mar 13, 2023 06:48PM

va...@google.com <va...@google.com> Jul 3, 2023 09:07AM

su...@google.com <su...@google.com> Jul 4, 2023 02:40PM

gp...@travix.com <gp...@travix.com> #14Jul 26, 2023 02:41PM

jr...@bgrove.com <jr...@bgrove.com> #15Jul 26, 2023 02:45PM

gp...@travix.com <gp...@travix.com> #16Jul 27, 2023 11:53AM

[Deleted User] <[Deleted User]> #17Jul 31, 2023 12:15AM

ri...@focus-bc.com <ri...@focus-bc.com> #18Aug 4, 2023 10:53PM

ni...@unifiedpost.com <ni...@unifiedpost.com> #19Aug 25, 2023 08:26AM

cr...@tokinomo.com <cr...@tokinomo.com> #20Oct 4, 2023 07:44AM

pi...@extendaretail.com <pi...@extendaretail.com> #21Oct 25, 2023 11:39AM

it...@gcp.education.gov.il <it...@gcp.education.gov.il> #22Dec 10, 2023 12:50PM

la...@rome2rio.com <la...@rome2rio.com> #23Dec 20, 2023 02:55AM

de...@gmail.com <de...@gmail.com> #24Jan 2, 2024 04:38PM

in...@traceable.ai <in...@traceable.ai> #25Jan 30, 2024 06:33PM

ri...@google.com <ri...@google.com> #26Mar 4, 2024 07:45PM

ba...@google.com <ba...@google.com> May 21, 2024 11:06AM

ku...@google.com <ku...@google.com> May 30, 2024 01:23PM

el...@gmail.com <el...@gmail.com> #27Jun 11, 2024 01:22PM

se...@gmail.com <se...@gmail.com> #28Aug 26, 2024 02:34PM

ta...@google.com <ta...@google.com> #29Sep 5, 2024 08:45AM

Ru...@tbint.de <Ru...@tbint.de> #30Oct 24, 2024 11:35AM

el...@gmail.com <el...@gmail.com> #31Oct 24, 2024 01:20PM

ri...@google.com <ri...@google.com> #32Jan 9, 2025 07:05PM

Add comment

Issue metadata