I'm familiarizing myself with the Pangolin API to develop some automations (such as automatically adding a defined IP ruleset to every resource I create). I've encountered the following errors so far in testing:
1. While trying to delete an org, I receive a 500 "unknown error" status code. Relevant logs and screenshots are attached.
Is this possibly bug behavior?
pangolin | 2025-05-30T01:13:30.755987257Z 2025-05-30T01:13:30.755Z [error]: User not authenticated
pangolin | 2025-05-30T01:13:30.756105083Z Stack: UnauthorizedError: User not authenticated
pangolin | 2025-05-30T01:13:30.756126071Z at uo (file:///app/dist/server.mjs:12:17850)
pangolin | 2025-05-30T01:13:30.756139601Z at Vi (file:///app/dist/server.mjs:31:19673)
pangolin | 2025-05-30T01:13:30.756154873Z at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
pangolin | 2025-05-30T01:13:30.756168479Z at next (/app/node_modules/express/lib/router/route.js:149:13)
pangolin | 2025-05-30T01:13:30.756181529Z at file:///app/dist/server.mjs:25:21061
Below screenshot showing a successful get listing the org as valid:
And API key permissions:
2. Unable to GET or DELETE roles (returns 404/400), but able to create successfully
I can also create a role successfully:
But it fails to GET the role I just created...
The role is seen in the GUI so I can confirm it exists there:
And from the PUT, I know it's roleId is "8", so when I pass that in the body of a DELETE, I receive a 400:
For brevity, I won't add more but I'd love to work with the developers to contribute documentation fixes if nothing else - I'm not a software developer, but if I'm pointed to where in the code these endpoints are at least documented, I'd be happy to contribute something there. Thanks!
Originally created by @kmanwar89 on GitHub (May 30, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/805
Originally assigned to: @miloschwartz on GitHub.
Hi,
I'm familiarizing myself with the Pangolin API to develop some automations (such as automatically adding a defined IP ruleset to every resource I create). I've encountered the following errors so far in testing:
### 1. While trying to delete an org, I receive a 500 "unknown error" status code. Relevant logs and screenshots are attached.
Is this possibly bug behavior?
```
pangolin | 2025-05-30T01:13:30.755987257Z 2025-05-30T01:13:30.755Z [error]: User not authenticated
pangolin | 2025-05-30T01:13:30.756105083Z Stack: UnauthorizedError: User not authenticated
pangolin | 2025-05-30T01:13:30.756126071Z at uo (file:///app/dist/server.mjs:12:17850)
pangolin | 2025-05-30T01:13:30.756139601Z at Vi (file:///app/dist/server.mjs:31:19673)
pangolin | 2025-05-30T01:13:30.756154873Z at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
pangolin | 2025-05-30T01:13:30.756168479Z at next (/app/node_modules/express/lib/router/route.js:149:13)
pangolin | 2025-05-30T01:13:30.756181529Z at file:///app/dist/server.mjs:25:21061
```
<img width="1303" alt="Image" src="https://github.com/user-attachments/assets/44967cb7-dac7-43d1-a903-a84b1a3857aa" />
Below screenshot showing a successful get listing the org as valid:
<img width="1261" alt="Image" src="https://github.com/user-attachments/assets/53cbfdff-bea0-43eb-850e-65159b29fe7e" />
And API key permissions:
<img width="1650" alt="Image" src="https://github.com/user-attachments/assets/c4ac9b05-d932-4a0a-9308-98cca4ad2a6c" />
### 2. Unable to GET or DELETE roles (returns 404/400), but able to create successfully
I can also create a role successfully:
<img width="1315" alt="Image" src="https://github.com/user-attachments/assets/09d67ec5-4a21-4537-a39c-2ee5f091ad4e" />
But it fails to GET the role I just created...
<img width="1348" alt="Image" src="https://github.com/user-attachments/assets/9c605491-6eeb-4271-9d33-3777ff65c972" />
The role is seen in the GUI so I can confirm it exists there:
<img width="931" alt="Image" src="https://github.com/user-attachments/assets/1d40349c-bba7-4a93-83d2-1df938314bbf" />
And from the PUT, I know it's roleId is "8", so when I pass that in the body of a DELETE, I receive a 400:
<img width="1314" alt="Image" src="https://github.com/user-attachments/assets/58f0f92e-2183-4585-a849-63f67ea2ef44" />
For brevity, I won't add more but I'd love to work with the developers to contribute documentation fixes if nothing else - I'm not a software developer, but if I'm pointed to where in the code these endpoints are at least documented, I'd be happy to contribute something there. Thanks!
@oschwartz10612 commented on GitHub (May 31, 2025):
Hi thanks for testing all of these things in the api. They sounds like real bugs that may have arisen from the shared code between both the integration api and dashboard API. Ill ping @miloschwartz to take a look.
<!-- gh-comment-id:2925264795 -->
@oschwartz10612 commented on GitHub (May 31, 2025):
Hi thanks for testing all of these things in the api. They sounds like real bugs that may have arisen from the shared code between both the integration api and dashboard API. Ill ping @miloschwartz to take a look.
I'll work on fixing the GET in the next release (seems to be missing from the router hence the not found error).
For the DELETE, it's not documented well, but the roleId that will be deleted needs to be passed in the URL params. The roleId in the body, is the new role to which the users previously present in the deleted role will be assigned.
<!-- gh-comment-id:2941308049 -->
@miloschwartz commented on GitHub (Jun 4, 2025):
I'll work on fixing the GET in the next release (seems to be missing from the router hence the not found error).
For the DELETE, it's not documented well, but the roleId that will be deleted needs to be passed in the URL params. The roleId in the body, is the new role to which the users previously present in the deleted role will be assigned.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @kmanwar89 on GitHub (May 30, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/805
Originally assigned to: @miloschwartz on GitHub.
Hi,
I'm familiarizing myself with the Pangolin API to develop some automations (such as automatically adding a defined IP ruleset to every resource I create). I've encountered the following errors so far in testing:
1. While trying to delete an org, I receive a 500 "unknown error" status code. Relevant logs and screenshots are attached.
Is this possibly bug behavior?
Below screenshot showing a successful get listing the org as valid:
And API key permissions:
2. Unable to GET or DELETE roles (returns 404/400), but able to create successfully
I can also create a role successfully:
But it fails to GET the role I just created...
The role is seen in the GUI so I can confirm it exists there:
And from the PUT, I know it's roleId is "8", so when I pass that in the body of a DELETE, I receive a 400:
For brevity, I won't add more but I'd love to work with the developers to contribute documentation fixes if nothing else - I'm not a software developer, but if I'm pointed to where in the code these endpoints are at least documented, I'd be happy to contribute something there. Thanks!
@oschwartz10612 commented on GitHub (May 31, 2025):
Hi thanks for testing all of these things in the api. They sounds like real bugs that may have arisen from the shared code between both the integration api and dashboard API. Ill ping @miloschwartz to take a look.
@miloschwartz commented on GitHub (Jun 4, 2025):
I'll work on fixing the GET in the next release (seems to be missing from the router hence the not found error).
For the DELETE, it's not documented well, but the roleId that will be deleted needs to be passed in the URL params. The roleId in the body, is the new role to which the users previously present in the deleted role will be assigned.
@miloschwartz commented on GitHub (Jun 5, 2025):
Should be fixed in 1.5.0. Let me know if for some reason it's not!