For context, the motivation is to let more of the settings be purely derived from config files and to make the configs more explicit.
Appending /v1/data is something that the end users can do by setting this on the URI. Making the URI be read from config and not get modified further lets us potentially introduce a base OpaS3SecurityMapper implementation in the future that sends a standard-format (which we'd need to decide upon) OPA request to whatever URI the user configured (similar to what the Trino OPA plugin does)
For context, the motivation is to let more of the settings be purely derived from config files and to make the configs more explicit.
Appending
/v1/datais something that the end users can do by setting this on the URI. Making the URI be read from config and not get modified further lets us potentially introduce a base OpaS3SecurityMapper implementation in the future that sends a standard-format (which we'd need to decide upon) OPA request to whatever URI the user configured (similar to what the Trino OPA plugin does)