Way to preserve upload-time metadata for pull-through repository

Aberta
#1,371 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
api, backend

Direção de pesquisa

Start by reviewing the simple repository API JSON responses mentioned in the issue and the related constraints in #1370. Define how a pull-through repository should preserve the source upload-time metadata, including whether this is configurable, and verify that copied packages expose the expected original timestamp.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Feature Triage-Needed

Is your feature request related to a problem? Please describe.
I would like to use pulp's python plugin for a pull-through repository that mirrors pypi, so that I always have packages I depend on available locally (even if pypi goes down or a package is pulled from it, similar to left-pad). However, I also make use of dependency cooldowns using pip's --uploaded-prior-to and uv's --exclude-newer. A pulp pull-through repository shows the source upload-time metadata before it is copied, but after copying shows the time it was copied (uploaded to pulp). This prevents me from using pulp as a pull-through mirror alongside --uploaded-prior-to/--exclude-newer.

The upload-time changing when the package is copied seems like it could generally cause confusion or difficulty anyway.

Describe the solution you'd like
I don't have a clear idea of how this could be solved, but it makes sense to me for pull-through repositories to be transparent, and not change the upload-time metadata. Perhaps it could be an option when enabling pull-through?

Additional context
#1370 currently prevents actually using --uploaded-prior-to/--exclude-newer, but inspecting pulp's simple repository API JSON responses has made it apparent that this would be an issue for my use-case even if #1370 were fixed.

Linguagem predominante
Python
Estrelas
49
Forks
88
Merge médio
1d 10h
PRs com merge (30d)
31

Guia de contribuição

Abrir o guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pulp/pulp_python

Todas as issues de pulp/pulp_python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.