Hi @stevedennis, Thanks for the reply. It turns out my default nginx server was intercepting all http traffic and not allowing requests to get to the Proget server. I solved the issue by disabling the default server (removing it from sites-enabled) and making some config changes to the Proget nginx config file to stop the server from redirecting http traffic to https.

Hi @chrisblankde, Can you please tell me what metadata you are trying to update? If it is just the version, you can use the Repackage API. If it is something other than the version, in ProGet 2023, we added the ability to edit the upack metadata directly in ProGet. You can do that by navigating to the package version in your universal package feed and then click "Edit Package" in the upper right corner. If neither of those options works for you, then what you suggested (download/extract/edit/repack/upload) would be the way to handle this. Thanks, Dan

@mness_8576 thanks! We definitely welcome feedback on the UI/UX - this is a new feature, so there's a lot of room to improve :)

Hi @jimbobmcgee, I just wanted to let you know that we just released Otter 2023 and it includes the name filter on the List action type on the Infrastructure API. Thanks, Rich

Hello, The Docker API is supposed to only support based bearer authentication, but in previous versions (v5) it also worked with Basic auth. There's a sample script on this page that shows how you can authenticate: https://docs.inedo.com/docs/proget-docker-semantic-versioning Cheers, Alana

@mcascone yep, that's a good way of putting it!

Thanks for the detailed writeup! We've just published v1.0.1 of pgscan that should fix the issues you've described. v1.0.1 will now actually write errors and other info to the console like it's supposed to. There is also now a --api-key argument to allow it to authenticate with ProGet. Downloads are here: https://github.com/Inedo/pgscan/releases

Thanks John. We have tried the FindPackagesById endpoint and this is completing in 75ms which is much more expected. We are going to continue with this API to see if we can get what we need from it.

Thank you. We have upgraded and now it works. For clarity any REST API call would not work before the upgrade.

Hi Chris, You'll need to run the NuGetPackagesV2_SetListed method instead. In order to this, you'll need to mark it as non-internal; this can be done with a simple database query... UPDATE [__StoredProcInfo] SET [Internal_Indicator] = 'N' WHERE [StoredProc_Name] = 'NuGetPackagesV2_SetListed' This will be also be updated in 5.2.10 as PG-1549.

AllowFunctionAccess_Indicator is an Y/N indicator to allow access to the credential values if they are encrypted.

Yes. that is correct. I believe there is a plan to add security into the API.

At of ProGet 5.1, that's the only way. We may add support for this in a future version if we get more feature requests

Thanks, I've filed this as a bug here: BM-3307

As a followup, it's worth mentioning that this occurs specifically when directory providers are switched. The "Active Directory (New)" user directory requires the user@domain.tld format, so switching from the previous "LDAP & Active Directory" user directory (which supported netBIOSdomain\user) no longer can impersonate.

Unfortunately the Native API is essentially a database wrapper, and one of the few things that can't be handled at the database layer is encryption. While we want to create a resource credential API at some point, in the meantime, the only workaround would be to encrypt/decrypt the secrets yourself, using the Encryption Key stored in your configuration file.

Here is a working PowerShell example (v6.1+): Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/builds/deploy?applicationName=ApiTest&releaseNumber=1.2.3&buildNumber=1&key=<api-key>" For pre-v6.1 versions, the equivalent is: Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/packages/deploy?applicationName=ApiTest&releaseNumber=1.2.3&packageNumber=1&key=<api-key>" I have also put in a doc change request to clarify the endpoint names. Additional note: -UseDefaultCredentials would be required if Integrated Authentication were enabled.

Currently assets do not have any user-definable metadata like this, I guess because that would make them a lot like packages? Assets also aren't intended to be like a "SharePoint replacement", which is why we don't want to put a lot of extra features like versioning, etc. These are also hard to replicate, etc. That being said, we are open to changes, so please consider using the Feature Request Process. Note that, we also want to evaluate "why" and "how this would be used", and that's part of the feature/change process.

This is a known issue with the native API. The behavior is certainly not desired, and we are planning to develop a new feed management API in the future, so we will address this issue at that time. in the meantime, please be careful when using the Native API; it's a low-level API and doesn't always validate like you would expect. Note you can also delete the feed using the NativeAPI if you accidentally do that.

This is actually an artifact of the OData specification from when ProGet was first developed - that was actually the preferred format specified, and NuGet.org didn't support $format=json, so we just followed the OData spec. Anyway, those are just .NET DateTime Ticks in there (and the +0 just indicates UTC), so in your example it would just be: new DateTime(636650168208570000, DateTimeKind.Utc) Of course, if we had it to do over again, it would be something more sensible like ISO-8601.