stackhpc / stackhpc/ansible-collection-pulp
Changing sync policy for the remote fails
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Once repository is created and synced using a remote, changing it's synchronisation policy to a different than initial one results in HTTP 400 Bad Request. This is normally supported by Pulp using direct REST calls.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Reproduce the failure by creating and syncing a repository remote, then changing its synchronization policy through the collection and compare the update with Pulp's direct REST behavior. Done means an existing remote can change policy without an HTTP 400 response, with coverage added where the collection currently tests remote updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100