Project

Profile

Help

Issue #6221

closed

Bindings Issues at Install, Undocumented Fix

Added by CodeHeeler about 4 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
(Total: 0:00 h)
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
API Bindings, Dev Environment, Documentation
Sprint:
Sprint 69
Quarter:

Description

The bindings had a recent fix with issue #6204. The bindings are published nightly to PyPI but this doesn't cover prerelease changes.

Dev environment was broken due to outdated bindings.

Solution was to uninstall the old bindings, then pip install from PyPI again using --pre flag.

This needs to either be documented wherever we discuss bindings such as for pulpcore and pulp-rpm (and likely other plugins): https://pulp-rpm.readthedocs.io/en/latest/bindings.html#python-client https://docs.pulpproject.org/client_bindings.html#python-client-for-pulpcore-s-rest-api

OR

There needs to be something added to our installer/roles so that this is handled and so long as a dev has all up to date repos, the bindings should be generated or installed as part of the process. (I tried a to re-provision the vagrant just in case, and that didn't work, but I did not go so far as to destroy and re-up so if that handles it already and is the only way, apologies.)


Sub-issues 3 (0 open3 closed)

Ansible Plugin - Task #6390: Document bindings installation on dev environmentCLOSED - CURRENTRELEASEfao89

Actions
RPM Support - Task #6395: Document bindings installation on dev environmentCLOSED - CURRENTRELEASEfao89

Actions
Debian Support - Task #6396: Document bindings installation on dev environmentCLOSED - CURRENTRELEASEfao89

Actions

Also available in: Atom PDF