Permit

sample.tar.gz

docker-compose.yml

external_data.json

Hi <@U04K8QLP01K> thanks for reporting this!
<@U02CN8CVBJL>, <@U033FPT0BFH> can you take a look please

<@U04K8QLP01K> That’s weird indeed.
However, I would be surprised if that has to do with the introduction of the `PATCH` method in data updates.
<https://github.com/permitio/opal/commit/18dbe29dbf520cc2f4e6c721d2ddb1067b992e40|This change> would be more suspicious as it has to do with the actual execution of OPA, Although I also don’t see why it should have any affect.
Another option is OPA somehow changed its CLI behavior (although found nothing suspicious in <https://github.com/open-policy-agent/opa/blob/main/CHANGELOG.md|change log>).
I will take a deeper look, hopefully get to it tomorrow.

<@U04K8QLP01K>
I believe this has to do with this <https://github.com/open-policy-agent/opa/issues/5879|change> which was introduced in the latest OPA version - v0.56.0.
(I’ve been able to make the external data show up again when building a custom `OPAL 0.7.4` that uses an older `OPA 0.55.0` ).

This change means that OPA treats any `.tar.gz` as a bundle - which means it takes over the policy &amp; data roots (overwriting any other files supplied).
Breaking changes in OPA are generally out of our control. I can suggest:
1. trying to add the external data file to the tar file.
2. extracting the tar and passing it to opa as a directory (so it won’t be read as a bundle).
3. Maybe this guide can help? - <https://www.openpolicyagent.org/docs/latest/management-bundles/#multiple-sources-of-policy-and-data>

<@U02BJ8MGVG8> - Wondering if there’s maybe another OPA tip you can offer for this scenario ?

please file an issue if you’ve got a use case that broke through that — supposedly innocent — change!

<@U04K8QLP01K> - I’d leave it to you to (if you choose) to open this as an issue with OPA.