Replies: 2 comments 4 replies
-
Hi @9ing can you share your OPAL-server and OPAL-client logs?
This sounds like the client isn't connected correctly to the server, try to see in the logs if it connected and with each topics |
Beta Was this translation helpful? Give feedback.
-
Hi @9ing, excellent question! You did the external config redirect beautifully, but the fetching of this config is the "base config" or "complete picture" data that OPAL client will fetch after every fresh connection to OPAL server (i.e: on first connection, or after a disconnect and reconnect). OPAL client also has a separate mechanism for real time updates, and the data topics matter here.
Hope that helps, let me know if you have more questions. |
Beta Was this translation helpful? Give feedback.
-
Hi
My OPAL Server OPAL_DATA_CONFIG_SOURCES was setting like this:
{ "external_source_url": "https://your-api.com/path/to/api/endpoint" }
And my OPAL client would get this response from external_source_url:
{ "entries": [ { "url": "https://api.yourservice.com/v1/data", "topics": [ "test_topic" ], "dst_path": "", "headers": { "Authorization": "jwt1" } } ] }
(My OPAL client didn't set any OPAL_DATA_TOPICS)
I got my policy data from this entry url indeed. And I think OPAL client would subscribe topic "test_topic".
I called OPAL server "Publish Data Update Event API" to notify OPAL client topic "test_topic" was update, but OPAL client didn't
receive any notification to fetch policy data.
So is OPAL client does not subscribe external data sources response topic originally?
But if it does not subscribe external data sources response topic, why I still need to put topic in entries response?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions