Actions
Issue #5642
closedPulp client configuration object instantiation doesn't work correctly
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
The constructor of the Configuration object does not work as expected:
In [16]: pulpcore.Configuration(username="admin", password="password", host="http://pulp3-sandbox-debian10:80").host
Out[16]: 'http://localhost:24817'
Updated by fao89 over 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 61
Updated by dkliban@redhat.com over 4 years ago
- Subject changed from Pulp client api is broken to Pulp client configuration object instantiation doesn't work correctly
Updated by fao89 over 4 years ago
In [1]: from pulpcore.client import pulpcore
In [2]: pulpcore.Configuration(username="admin", password="password", host="http://pulp3-sandbo
...: x-debian10:80").host
Out[2]: 'http://pulp3-sandbox-debian10:80'
(pulp) [vagrant@pulp3-source-fedora30 pulpcore-client]$ pip list | grep pulp
pulp-file 0.1.0b5.dev0 /home/vagrant/devel/pulp_file
pulp-rpm 3.0.0b8.dev0 /home/vagrant/devel/pulp_rpm
pulp-smash 1!0.7.0
pulpcore 3.0.0rc8.dev0 /home/vagrant/devel/pulpcore
pulpcore-client 0.0.0 /home/vagrant/devel/pulp-openapi-generator/pulpcore-client
pulpcore-plugin 0.1.0rc8.dev0 /home/vagrant/devel/pulpcore-plugin
Updated by rchan over 4 years ago
Removing from sprint since we don't have enough capacity to do right now.
Updated by dkliban@redhat.com over 3 years ago
- Status changed from NEW to CLOSED - NOTABUG
I suspect that this is fixed in the latest client.
Actions