Hi Matthew, After discussing with our team they think this could be related to Windows Integrated Authentication (if it is enabled) or a configuration issue in your nuget.config file.. Can you try to use fiddler to help pinpoint the issue? Also, have you enabled CEIP in ProGet? That would give us some visibility to you errors. Thanks, Jason

Hello, Sorry for the confusion. For your solution you would need two separate feeds. One for normal package, one for symbols. Thanks, Jason

So I looked over OT-331, and while close, I am looking for each role to report the status of each server that has that role assigned to it, and whether it has drifted or is current. Thanks!

Hello, In ProGet all you just need to modify your baseurl in the advanced settings. However, for the actual ssl setup we suggest using "letsencrypt" which you can learn more about here: https://blog.georgejose.com/moving-my-http-website-to-https-using-letsencrypt-haproxy-and-docker-deb56ff6be9b Hope this helps! Thanks, Jason

Hello, I think what you are trying to do can be accomplished by adding a restriction for "View & Download Packages" to "any" feed for "Authenticated" users. Then add whatever permission to the API user. Use the Test Privileges button to verify. [image: 1562936601335-92ad03ea-b42d-411b-bd45-e1afd1f6d5fc-image.png] Thanks Jason

We don't have a bug bounty program, but please submit a ticket if you find anything and we will immediately address it.

Hi Fabrice, can you open a feature request for this? It's a ticket, and we can more easily track/prioritize it on our end this way. We generally avoid just adding "pagination and order by" in data lists because it usually means you're having to click through page after page and play around with order to find what you're looking for. We'd like to make it much easier :) So to do that, we'd love to learn more about the use case, because we have a feature on our roadmap to give a lot more insight into "which project uses a component", and I think you're definitely on the right track by using those headers. So screenshots, etc., would be great (and having this tracked in that feature request is so much simpler for us to manage internally). We can update this post once we have more insight, and if anyone is curious we can just reply with more info here :)

ProGet does not have the concept of "public" or "private" feeds, you can instead grant the "Anonymous" user certain permissions, including viewing and publishing packages. ProGet Free Edition does not allow feed-level permissions, only system-level permissions. So you can grant "Anonymous" whatever rights you want, just not at a feed-level.

Hi Gordon, Looking at the code, it should work if the ReleaseNotes element is within PackageManifest under Metadata. This would be the schema we use: https://docs.microsoft.com/en-us/visualstudio/extensibility/vsix-extension-schema-2-0-reference?view=vs-2019 Thanks, Jason

Hi Giorgi, Are you using Windows Authentication for your instance of ProGet? Thanks, Jason

Warn will still automatically advance. I was able to utilize the Set-ReleaseVariable as you suggested. Thanks!

this is solved but i'm still replying

Thanks very much for the clarification

Aha, it will also be included in BuildMaster... not sure why I got stuck on Otter. I guess it was on my mind because we just had a maintenance release today :) This feature is also scheduled for BuildMaster v6.1.10 on July 19

Hi Jared, According to the docs - It’s currently not possible to mirror another private registry. Only the central Hub can be mirrored. However, we do support connectors to another repository and are nearing completion on a project for docker replication between ProGet instances. Thanks, Jason

hi Jonathan, can you help me with a test case on the duplicate server issue? Are you trying do an infrastructure import that has the same server name defined twice in the same JSON document?

Hi Tigran, We currently do not support pytest but will take this into advisement and treat this ticket as a feature request Thanks, Jason

Thanks Philipe; all operation documentation is automatically updated within the software once the latest version of the relevant extension is installed (i.e. the Windows extension in this case). The documentation on the website will also get updated with any minor version of the software is released, or the Inedo.SDK is updated. Hope this helps, -Tod