You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With 3.70, my understanding is there are breaking changes in the bindings. There are good reasons for them (not recapped here), but my understanding is these changes are best for our community in the long term. There is a roundup of the breaking changes here.
That being said, I think bindings users need clear documentation on two things. This ticket is tracking the creation of those docs.
How to port bindings usage with a clear example for each breaking change they need to handle.
How to build the old bindings yourself if you don't want to port right now.
The text was updated successfully, but these errors were encountered:
In pulpcore, we should update this page to point to the oa-gen docs.
pedro-psb
changed the title
Porting guide to bindings for 3.70 and how to build pre 3.70 versions
[PULP-398] Porting guide to bindings for 3.70 and how to build pre 3.70 versions
Mar 19, 2025
How to build the old bindings yourself if you don't want to port right now.
This is not currently supported (e.g, generating old bindings for pulpcore>=3.70). That would be a new "feature" of the pulp-openapi-generator to allow that.
It's actually really simple to add (and I can add it if there is still the feeling it's needed), but I just think it would be unhelpful to add that knob without tests (and without explicit downstream/upstream requests). IMHO it's just unlikely to work, since there couplings between the generator and pulpcore for some version ranges.
With 3.70, my understanding is there are breaking changes in the bindings. There are good reasons for them (not recapped here), but my understanding is these changes are best for our community in the long term. There is a roundup of the breaking changes here.
That being said, I think bindings users need clear documentation on two things. This ticket is tracking the creation of those docs.
The text was updated successfully, but these errors were encountered: