Thank you, I only have one type of rpm package
The name and versioning are like the following
The API will call like this
POST https://artifacttest02.dev.petrolink.net/packages/bulk-delete
AHAntiCsrfToken=Tps3B1Cx9nbQARqwWTHx6rE0NqoFG4N8Ujyn6fPvO%2FTQXJRFIHFbkuNblk7ds7E862rGTM9eRWP%2BSXgvnC70Pw%3D%3D&ids=7%3A%3Assdh%3A0.5.0.177-1.el.7.centos%2C7%3A%3Assdh%3A0.5.0.179-1.el.7.centos
Response Status code is 200
Thank you, however I am not sure since I have not retested the installation, from my memory, it does not seems to add write permission either for my local (windows 11), as I was not seeing the Network Service there initially and had to add manually add network service. Same case in a separate testing server (Windows Server 2025 Standard). If you see that in older Windows may be because in later windows this behavior is changed, but not sure.
Ok thank you for confirmation. The whoami is useful for troubleshooting things, though not necessary for day to day, so it would be useful to be implemented.
I was stuck with an issue unable to publish to npm feed. Had this available, I would be able to fix it quicker (the issue had multiple sub-issues) as I was not even sure whether I was logged in correctly or not.
I think you found same issue like me, you probably need to grant read permission for NetworkService to C:\ProgramData\Inedo and C:\ProgramData\ProGet . You may also need to do the same if you do any other data storage. The Installer does not add the read permission.
I am not sure whether this is documented somewhere but it seems proget does not support cli "npm whoami" as it returns 404, is it true? If it is not true can you give either how to do it or which documentation for doing that?
I am talking about https://docs.npmjs.com/cli/v11/commands/npm-whoami
Hello not sure whether this has been reported, using 2025.9 (Build 16) version, I have 2 RPM feeds and when I check bulk edit for deleting multiple packages, it does not seems to work on both feeds. I can see the API call sent correctly (POST and payload are sent) and returned 200 but there is nothing done on rpm packages. I checked npm feed and it seems to work in npm so likely rpm feed specific issue (though I do not check other feed types)
Also a suggestion, when user delete package the page ideally stay on same page, instead redirecting to main feed on deleting single package and redirecting to first page when deleting using bulk edit