Project

Profile

Help

Story #8083

As a user, I can specify `headers` as an option for all remote types

Added by bmbouter 12 days ago. Updated 12 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:

Description

Use Cases

  1. For RPM content, oracle linux needs headers sent for the server to respond properly. You can see this work started in these PR: https://github.com/pulp/pulpcore/pull/1041 and https://github.com/pulp/pulp_rpm/pull/1896/

  2. For syncing content using Alternate Content Sources from Pulp instances in EC2, e.g. RHUI servers it also requires headers to be sent with downloads.

Solution

Given that there are two use cases for headers, and headers are a generic HTTP downloading concept, let's add them to Remote and have the DownloaderFactory create downloaders with them.

These headers are ultimately passed to aiohttp as a dictionary per their docs so let's store the field in DRF as a DictField. Probably defined as DictField(child=CharField()).

That means on Remote the new field would be:

headers = models.JsonField(null=True)

History

#1 Updated by bmbouter 12 days ago

  • Description updated (diff)

#2 Updated by bmbouter 12 days ago

  • Description updated (diff)

#3 Updated by bmbouter 12 days ago

  • Description updated (diff)

#4 Updated by daviddavis 12 days ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

Please register to edit this issue

Also available in: Atom PDF