Kevin Glavin

To put a very fine point on the issue, it is _strictly_ the `grant_strings` portion of the `boundary_role` resource that fails on _any_ operation that modifies grant strings. The `grant_scope_id`...

tl;dr: removing `max_open_connections` from the boundary configuration database stanza resolves this issue and more. Deeper down the rabbit hole... I got suspicious that the issue I was having is not...

fyi, this issue still holds in: - rules_js v1.32.0 - rules_pkg v0.9.1 - rules_python v0.25.0 I'm still working around it with a local change to the python approach last attributed...

any traction here?