This message was deleted.
# opal
s
This message was deleted.
j
So the server is only updating the client only on Add policy file (image attached)
o
So no initial policy? That shouldn’t be the case. Which version of OPAL is this?
j
The client gets the initial policies. But then when the server receives the webhooks, the server only updates the client on file add (it doesn't update on deleting / updating code)
The server version : 0.5.0 The client version : latest (I think it's 0.5.0 also)
Here we can see 2 webhook events : 1. The one that added a rego file, the Server updated the client. 2. The one that updated the policy rego code, did not notify the client
r
Hi @Jack Geek - looks like a bug I’ve recently fixed, but we haven’t released a new OPAL version since. You can try using
permitio/opal-server:0.5.2-rc
and see if it solves the issue (let us know!)
j
Hello, It didn't work either, when I add some code to existing policy, there is nothing there Both client and server are versionned : 0.5.2-rc
The 0.5.2-rc server does not update the client for any operation : add file, delete file, update code
o
@Jack Geek - to be clear Is the problem you’re not getting the initial policy loaded, or only follow-on updates ?
r
@Jack Geek - I don’t think it has to do with differences between adding / deleting etc - for some reason the updates not always work (regardless of their content). Do you set
OPAL_BROADCAST_URI
? and
UVICORN_NUM_WORKERS
? would you share their values?
j
@Or Weis, the problem is on the follow-on updates. For the version 0.5.0, I only receive updates for adding rego files, for version 0.5.2-rc I don't receive any update. @Ro'e Katz , no I don't set them, please find my server kube config attached
o
@Jack Geek, if you don't set a broadcaster you have to set
UVICORN_NUM_WORKERS
to 1. Otherwise the different workers in the server won't propegate messages between them
👍 1
j
Hi @Or Weis, I will try it first thing in the morning and let you know. Thanks
💜 1
Hi @Or Weis, that doesn't fix the issue, for the version opal-server:0.5.2-rc , the server does not update nothing
o
@Ro'e Katz do you other recommendations here ?
j
new commits detected but no tracked files were affected: '3876d277365be7a08f4c6a4603ed78ed49c271d6' -> '21e2795a961db9d7b44da1c20da547ac9c69d274' Although, I made an update to one policy and deleted another policy file
o
Debugging together on a call : we reduced the replica set, in addition to the number of workers above to have only one instance of OPAL when working without a broadcaster