Looks like updating policies is broken in `0.83.2`...
# helpt
Thomas Vander Wal
10/11/2022, 7:33 PMLooks like updating policies is broken in
0.83.2400 - Already existsThomas Vander Wal
10/11/2022, 7:34 PMMy hunch was it was trying to post a new policy but looks like it’s using the expected put on
/auth/policies/{policyID}n
Niro
10/11/2022, 7:47 PMHi @Thomas Vander Wal!
Can you please describe the exact scenario which causes the error?
t
Thomas Vander Wal
10/11/2022, 7:50 PMOf course! We have existing policies that give users access to specific repositories based on prefix. I went to add some additional actions but the save fails with that error after editing. I verified it in two separate environments running
0.83.2n
Niro
10/11/2022, 7:51 PMDo you see this failure only when updating the policy via UI?
t
Thomas Vander Wal
10/11/2022, 8:15 PMI haven’t tried with postman directly yet, but I can do that later today
n
Niro
10/11/2022, 8:20 PMThat's fine, I'm looking into it and update in the following hour. Thanks!
Niro
10/11/2022, 8:42 PM@Thomas Vander Wal I've verified there's indeed a bug in the underlying API.
I've opened https://github.com/treeverse/lakeFS/issues/4354 to track and fix it and will release a fixed version in the following 24 hours.
Thank you so much for bringing it to our attention! ✨
heart lakefs 1
Niro
10/12/2022, 5:49 PMHi @Thomas Vander Wal,
Wanted to give you an update that lakeFS v0.83.3 was release with the required fix!
https://lakefs.slack.com/archives/C017S6YFFSP/p1665596726271519
Let us know if there's anything else we can help with, and thanks again for reporting the issue! 🤘🏽
🙌 1
t
Thomas Vander Wal
10/13/2022, 2:49 AMThank you! Confirmed working on our environments now 🙂
2 Views