Pulpcore API client bindings should support configuring a port separately from the host

Open
#126 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
openapi, ruby
Domain
api

Research direction

Start with the Ruby bindings and the PulpcoreClient::Configuration object named in the issue. Trace how the host currently carries the port, then check the generated client configuration templates and related tests if present. Done means callers can configure port separately without relying on the host field.

Written by the indexing model from the issue text.

Description

Feature

Is your feature request related to a problem? Please describe.
Today, Pulpcore client requires port configuration to go in the URI's host field. This is in the context of the Ruby bindings, but I assume it applies to others as well. It would be cleaner to have the port be defined separately, just in case the host part of the URI is somehow cleaned of the port. It would be more explicit.

Describe the solution you'd like
The ability to create a PulpcoreClient::Configuration object with a port.

Describe alternatives you've considered
For now, we can include the port in the config object's host field.

Additional context
https://community.theforeman.org/t/katello-does-not-honor-host-port-for-pulp-calls/45231

Dominant language
Mustache
Stars
4
Forks
29
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp-openapi-generator

All issues in pulp/pulp-openapi-generator

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.