Ashutosh Narkar
Ashutosh Narkar
Fixed in https://github.com/open-policy-agent/opa/pull/6728.
@carabasdaniel wdyt about this update? The tests pass but you mentioned [here](https://github.com/open-policy-agent/opa/pull/6560#issuecomment-1945551475) that this could have potential issues. Is that still the case?
Closing this for now as there could be potential conflicts with our current implementation. Needs further investigation.
Adding a new flag to `opa build` to follow symlinks seems fine. This would require changes in the bundle reader. In the meantime if you'd like to improve the docs...
[Currently](https://sourcegraph.com/github.com/open-policy-agent/opa@d718975b5de4b05cf2c88d5a52efaa33e71b0f0e/-/blob/topdown/crypto.go?L304) OPA sets `Roots` and `Intermediates` field of the [x509.VerifyOptions](https://pkg.go.dev/crypto/x509#VerifyOptions). If we were to add a new builtin may that could take an object that allows users to optionally specify...
Sure @yogisinha!
@yogisinha what if we create a new builtin called something like `crypto.x509.parse_and_verify_certificates_with_options`. The second argument would be an object that allows users to optionally specify KeyUsages, DNSName and other options...
Yeah something like that.
@yogisinha it's difficult to give feedback this way. I would recommend you open a draft PR and folks can chime in. Thanks.
Hello @david-hamilton-bah thanks for the detailed issue and also for providing info on your use-case. From what I understand the app developers will author some policies and use the common...