Slackbot
07/13/2023, 3:48 PMOr Weis
07/13/2023, 3:54 PMBen Lieber
07/13/2023, 3:56 PMBen Lieber
07/13/2023, 4:02 PMopal-fetcher-postgres-opal_client-1 | 2023-07-13T16:00:19.739569+0000 | opal_common.utils |WARNING | Unexpected response code 503: {'detail': 'policy repo is not ready'}
I wonder if that could be the culprit?Or Weis
07/13/2023, 4:08 PMBen Lieber
07/13/2023, 4:12 PMBen Lieber
07/13/2023, 4:13 PMwait-for-it
command though, as the pip installed one wasn’t accessible, so I used the included .sh
script. Maybe I need to back up and troubleshoot that a bit more.Ben Lieber
07/13/2023, 4:22 PM~/.local/bin/wait-for-it
as it’s not in the path. Still get the same message about server not being available thoughOr Weis
07/13/2023, 4:24 PMPUT /v1/data/cities
2. But then the policy-repo contains data.json and that overrides what was written onto data Got policy bundle with 2 rego files, 1 data files,
Ben Lieber
07/13/2023, 4:25 PMOr Weis
07/13/2023, 4:26 PMAren’t multiple sources to be expected and merged?Policy data is supposed to be loaded as a baseline, and then changes merged on top of it. (CC: @Shaul Kremer , @Asaf Cohen, @Ro'e Katz - we should really enforce this order - instead of assuming it) Not sure why the Git server is slow, but let’s see if we can configure it to wait, or dealy
Ben Lieber
07/13/2023, 4:30 PMOr Weis
07/13/2023, 4:38 PM/policy
on the server waiting for a 200
before starting the opal-client
another option is to remove the data.json
file from the repo, or have the server ignore it with OPAL_BUNDLE_IGNORE
(https://docs.opal.ac/getting-started/configuration#common-opal-configuration-variables)