@dean-houston

Hello!

In the "fixed" version, it no longer sets the same feed to all other projects, which is good.

Less good is that it now instead empties the Feed(s) field for all except the most recently changed Project.

Best regards
Nils Nilsson

Hi!

I have a breaking issue in ProGet 2026, upgraded from 2025.27
The issue is that when I try to add a new permission/restriction for ["Specific User...", "Specific Groups..."] it no longer manages to search for those defined in my Active Directory and synced through LDAP.

Attempting to Test Privileges of a group that is assigned(and still seems to be in effect as I'm able to log in and administer using my domain account) it is also unable to search for users/groups.

I've verified that the LDAP connection is still healthy through the 'Test User Directories' dialog

This issue was found because after upgrading all my existing permissions that were scoped to a feed group no longer had an association to the migrated "Feed & Project Groups" that replaced them, thus leading to having to reconfigure all permissions.

Regards
Nils Nilsson

Hello!

When I'm adding new notifiers I'd like to be able to send a test message to check that it works as expected.

Best regards
Nils Nilsson

@gdivis

Hello!

I've tested containers audit a little bit and it seems to work well at first glance.
I could easily differentiate between a vulnerable image and one with no vulnerabilities, both from output and exit code.

Thank you for your work! :)

// Nils

Hello @atripp ,

I've now had a chance to try out the new version of PGUtil and the changes are working great.
Thank you for your assistance :)

Best Regards
Nils Nilsson

I've had a chance to test the new version of pgutil now and it works perfectly, thank you.

Best regards
Nils Nilsson

Hi @dean-houston .

Thank you for your response, it makes sense that you wouldn't prioritize this, as I assume my organization is quite an outlier where we need to have one policy for every application that utilizes ProGet.

Best Regards
Nils Nilsson

Hi @dean-houston

Thank you for the detailed response.

I'll dive into the properties set and retention create commands to see if the current implementations already cover our automation usecase.

Fair point about the API, then I'll continue to default to using PGUtil so that you at least have one less user depending on the API in case you want to supercede/deprecate it in the future :)

Best Regards
Nils Nilsson

Hello!

I'm working on setting up an automated configuration of feeds for new Products/Projects in my organization.

When reading the documenation for Create Feed I noticed that the API which expects a ProGetFeed.cs object supposedly would allow you to set many extended options for a feed, such as Connectors, or PackageStatisticsEnabled. ProGetFeed.cs
As far as I've been able to tell, none of these options are available for setting when creating through PGUtil which basically only allows you to specify Name and Type, and soon also Group as we discussed previously here.

My first question is if this disparity in options between API / PGUtil is intentional and that advanced usecases should primarily aim to use the API for interfacing?
Or if there are options available in PGUtil that maybe remain undocumented in helpstrings/web docs?

My follow up question is if you intend to/would consider extending the options available in PGUtil?
If you do not want to laden PGUtil with a ton of options, would it be possible to implement a "New Feed Template" so that the default value of at least Feed Features Downloads, Deployments, Usage, Software Component Analysis could be changed to Enabled instead of Disabled?

Best Regards,
Nils Nilsson

Hi!

I'm working on automating the setup of new "workspaces" in ProGet whenever my organization onboards a new product/project.

I've been reading the documentation for a way to create a new Package Policy without the use of Web GUI actions, but turned up empty handed.

Is there a already way that I haven't found? If not, is that something you'd be willing to add to your backlog to implement?

If it is something you would consider implementing, my request is that you can set the Risk Profile during creation, in addition to the three fields available when creating in the Web Gui.

Example:

pgutil security policy create \
--Name="New Policy" \
--Priority=<'Default' | 'Before Global' | 'After Feed'> \
--Feeds="nuget-feed, maven-feed, npm-feed" \
--RiskProfile='{ \
    "Exposure" : "<External | Internal>", \
    "Interface": "<Web Browser | Unspecified>", \
    "Outage"   : "<Unacceptable | Disruptive | Tolerable>", \
    "Breach"   : "<Unacceptable | Disruptive | Tolerable>", \
    "Tampering": "<Unacceptable | Disruptive | Tolerable>" \
}'

Best regards,
Nils Nilsson

Hi @atripp

That's great, thank you :)

The API/command for creating projects should be updated to allow you to specify:

• Group
• Description
• Feed

https://docs.inedo.com/docs/proget/api/sca/projects/create

So that creation can be controlled by a central process and not require manual GUI operations

Best regards
Nils Nilsson

Hello!

I wish to be able to create new feed & project groups programatically so that it can be automated.

My suggestion is that it's either
a) Exposed as a new endpoint/command
b) If a non-existent feed group is provided for an endpoint or a command, like /api/management/feeds/create https://docs.inedo.com/docs/proget/api/feeds/create it will create the feed group provided the token used has sufficient permissions.

Currently scenario b will return code 400 with the message "Feed group <group> not found." and create an ungrouped feed.

I tried to jack into the /administrations/feeds/feed-groups/edit endpoint used by the website but ended up just being redirected to the login page.

Best Regards
Nils Nilsson

@gdivis

Hello!

I've tested containers audit a little bit and it seems to work well at first glance.
I could easily differentiate between a vulnerable image and one with no vulnerabilities, both from output and exit code.

Thank you for your work! :)

// Nils