Project

Profile

Help

Issue #8971

closed

ImportError: cannot import name 'PulpAnsibleGalaxyApiCollectionsApi' from 'pulpcore.client.pulp_ansible'

Added by daviddavis over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

The tests on pulp_ansible are failing with this error. See last night's test run:

https://github.com/pulp/pulp_ansible/actions/runs/970115331

I believe this is caused by a recent change in pulpcore to how bindings are generated. I looked through the bindings and I believe the new bindings class name for the galaxy v3 collections endpoint is PulpAnsibleApiV3CollectionsApi. We could update to use this class name although it doesn't seem quite right (ie notice the lack of "galaxy" in the class name). That said, the old class name PulpAnsibleGalaxyApiCollectionsApi doesn't seem quite right either (notice there's no V3 in the name).

Actions #1

Updated by bmbouter over 1 year ago

What about GalaxyV3ApiCollections ?

Actions #2

Updated by fao89 over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to fao89
Actions #3

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST

Added by Fabricio Aguiar over 1 year ago

Revision 946c3563

Fix broken bindings

closes #8971

Actions #4

Updated by Anonymous over 1 year ago

  • Status changed from POST to MODIFIED

Added by Fabricio Aguiar over 1 year ago

Revision 72e31da8

Fix broken bindings

closes #8971

(cherry picked from commit 946c3563d8a6283758a43050fdd94c1228fb290e)

Actions #5

Updated by fao89 over 1 year ago

  • Sprint/Milestone set to 0.9.0
Actions #6

Updated by pulpbot over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF