Savin Cristi
06/11/2025, 9:03 PMSavin Cristi
06/11/2025, 10:50 PMSavin Cristi
06/12/2025, 8:57 PM"config": {
"method": "get",
"headers": {
"Accept": "application/json"
},
"fetch_on_boot": true,
"polling_interval_sec": 60
},
"topics": [
Still, the polling interval is not working, it will only fetch on boot. Am I missing something?Savin Cristi
06/17/2025, 8:00 AMKSM
06/17/2025, 5:36 PMHarshit Parikh
06/18/2025, 9:41 AMDai Zhang
06/23/2025, 5:22 PM400
and {"detail": "repo url or full name not found in payload!"}
error.
how could i do that, thanks a lot!Dai Zhang
06/24/2025, 3:34 AMModuleNotFoundError: No module named 'opal_common.monitoring.tracing_utils'
, what should i do to fixDai Zhang
06/24/2025, 3:37 AMOr Weis
06/25/2025, 12:55 PMKrishna Prasad A
06/26/2025, 10:53 AMOPAL_DATA_CONFIG_SOURCES
environment variable like this in my `docker-compose.yml`:
OPAL_DATA_CONFIG_SOURCES={"external_source_url":"<https://api.jsonbin.io/v3/b/685ce5fd8960c979a5b1a42b?meta=false>"}
But when I check the logs, I see a warning: "Serving default all-data route, meaning DATA_CONFIG_SOURCES was not configured!"
, and the data doesn't seem to be loaded at the path I expect (e.g., v1/data/rbac
is empty when I curl it).
I'm a bit confused about the different ways to configure data sources. For just fetching a simple, static JSON file from a URL like this, am I using the right approach with external_source_url
? Or is there a simpler or different configuration format I should be using for this basic case?
Any pointers or examples for loading a simple JSON file from a URL into OPA via OPAL would be super helpful for a beginner!
Thanks a lot!Kirk Daries
07/07/2025, 3:11 PMShoham Yamin
07/09/2025, 7:54 AMKirk Daries
07/09/2025, 1:55 PMDavid Hamilton
07/11/2025, 6:07 PMVaibhav Yadav
07/11/2025, 8:03 PMThilak Reddy
07/17/2025, 10:23 AMuvicornWorkers: 1
as we donโt have a backbone setupMathieu Viau
07/21/2025, 3:22 PMWilliam Afonso
07/22/2025, 6:53 AMHarshit Parikh
07/25/2025, 3:45 PMPrasenjit Roy
07/27/2025, 6:23 PMPrasenjit Roy
07/29/2025, 2:07 PMKirk Daries
07/31/2025, 12:46 PMAlonahmias
07/31/2025, 3:56 PMKirk Daries
07/31/2025, 5:55 PMpermit(
principal in Role::"Editor",
action in [
Action::"document:read",
Action::"document:write",
Action::"document:delete"
],
resource in ResourceType::"document"
);
permit(
principal in Role::"LimitedEditor",
action in [
Action::"document:read",
Action::"document:write",
],
resource in ResourceType::"document"
);
Start up the stack.
You'll notice the cedar agent returns empty: http://localhost:8180/v1/policies (cedar agent)
Confirm data is present at: http://localhost:7002/policy (opal server)Sourabh Krishna
08/01/2025, 1:03 AMDai Zhang
08/03/2025, 7:03 AMopal-client publish-data-update $token --src-url <http://mybillingserver.com/users> --src-config '{"headers":{"authorization":"bearer secret-token"}}'
it only needs a single field named src-url
to determine which datasource should be updates.
1. however, when using posgres table as datasource, this url would like to be "url": "<postgresql://postgres@example_db:5432/postgres>"
. Does that means I need to put each data source into different database, in a way like 1 table in 1 database
mode? It sounds wired.
2. I checked another option to trigger data update. i.e. using OPAL Server REST API. However, this method seems to be wrong when only putting url
in request payload like curl ... --header 'Content-Type: application/json' -d '{"entries":[{"url":"<postgresql://postgres@example_db:5432/postgres>"}]}'
. The opal server won't fill the blanks of other field but remain them as empty which cause opal-client failed to fetch data.
3. then i know maybe I should put the whole datasource config entry into the payload. it sounds wired too. Does that mean I should hard-code all the datasouce configuration into my client.
Is there some id
or other workflow, e..g I first go somewhere to get the full datasource configure then post the data update. Really confusing, thanks a lot!Dai Zhang
08/04/2025, 3:56 PM2025-08-04T15:45:25.978352+0000 | ddtrace.internal.writer.writer |ERROR | failed to send, dropping 1 traces to intake at <http://localhost:8126/v0.5/traces> after 3 retries
Jack Muller
08/18/2025, 8:22 PM๊น์ํ
09/07/2025, 6:09 AM