With #6020 <https://pulp.plan.io/issues/6020> *plugin_template* functional
tests now use *bindings* instead of making REST calls to pulp. This brought
the need for installing bindings for being able to run functional tests,
due to this, pbindings
<https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/templates/alias.bashrc.j2#L148-L177>
was introduced on pulp-devel role on ansible-pulp.

pbindings is an alias for pulp-openapi-generator script
<https://github.com/pulp/pulp-openapi-generator#generating-bindings>,
it takes three positional arguments: module name, language, and version.
When the optional version parameter is provided, it is used as the version
string. When it is not provided, the version reported by Pulp's status API
is used.

*Examples:*
- generating python bindings for pulp_file:
$ pbindings pulp_file python

- generating ruby bindings for pulp_file with '3.0.0rc1.dev.10' version
$ pbindings pulp_file ruby 3.0.0rc1.dev.10

*Pulp-devel, ansible-pulp, pulplift*
pulp-devel role, during provisioning, automatically installs the python
bindings for every plugin listed on pulp_install_plugins.
If you want to make use of this, please update your pulplift

Best regards,
Fabricio Aguiar
Software Engineer, Pulp Project
Red Hat Brazil - Latam <https://www.redhat.com/>
+55 11 999652368
_______________________________________________
Pulp-dev mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to