This message was deleted.
# opals
Slackbot
01/11/2023, 7:08 AMThis message was deleted.
o
Or Weis
01/11/2023, 7:16 AMThe log clearly shows that OPA rejects the policy provided with a rego_type_error’: ‘multiple default rules named allow found’
OPA Client: unexpected status code: 400, error: {‘code’: ‘invalid_parameter’, ‘message’: ‘error(s) occurred while compiling module(s)’, ‘errors’: [{‘code’: ‘rego_type_error’, ‘message’: ‘multiple default rules named allow found’, ‘location’: {‘file’: ‘Service1/rbac.rego’, ‘row’: 25, ‘col’: 1}}]}
Or Weis
01/11/2023, 7:16 AMYou can use OPA test to validate your Rego before pushing it to Git or bundle server
Or Weis
01/11/2023, 7:19 AMAlso your data source server seems to be serving the data with the wrong mime type: “Attempt to decode JSON with unexpected mimetype: text/html”
s
Sumesh Sukumaran
01/11/2023, 7:21 AMI was in the assumption that we can use the same rule name multiple times. And in the sample repo Rego file also it is using the same name.
o
Or Weis
01/11/2023, 7:21 AMYou can use the same rule name- but there can only be one default
👍 1
Or Weis
01/11/2023, 7:21 AMWhich I’d say makes sense ☺️
s
Sumesh Sukumaran
01/11/2023, 7:25 AMAnd regarding the mime type, I have added application/json in my github webhook. Other than that, do I need to add it anywhere else?
o
Or Weis
01/11/2023, 7:28 AMThe server which you point to with the URL in your data-update should also serve JSON; (unless you use a custom data-fetcher)
Or Weis
01/11/2023, 7:29 AMThis is the URL in the log - “https://9027-183-83-252-7.in.ngrok.io/policy-data”
s
Sumesh Sukumaran
01/11/2023, 7:33 AMGot it thanks alot
😇 1
2 Views