Several years ago, when Pulp3 first started shipping bindings, we didn’t use them in the tests directly. Instead to “test the bindings” we made a “bindings” runner with each repo containing a test script for the python bindings and one for the ruby bindings. You can see those for pulpcore for example here and here.
Now the functional tests themselves are expected to directly test by using the Python bindings themselves, so the “bindings” runner is redundant at this point. I propose we delete this to simplify the CI maintenance and reduce the minute runtime of the CI.
The Ruby bindings would no longer be tested, but arguably no one is writing ruby into these test files anyway. Additionally any problems we have between Python and Ruby bindings are an openapigenerator problem, not a Pulp problem, so we shouldn’t be focused on testing their project (my take).