Conversation
16f7486 to
03e61c7
Compare
c7e19ec to
6647217
Compare
gerrod3
left a comment
There was a problem hiding this comment.
This PR looks like it is coming along well.
5ad38d9 to
597818e
Compare
pulp_python/app/models.py
Outdated
| python_version = models.TextField() | ||
| sha256 = models.CharField(db_index=True, max_length=64) | ||
| sha256_metadata = models.CharField(max_length=64) | ||
| yanked = models.BooleanField(default=False) |
There was a problem hiding this comment.
@gerrod3 So, I take it that the python plugin does not have "immutable" content, since "yanked" is explicitly mutable?
The yanked attribute is not immutable once set, and may be rescinded in the future (and once rescinded, may be reset as well). Thus API users MUST be able to cope with a yanked file being “unyanked” (and even yanked again).
There was a problem hiding this comment.
Yeah I don't know what to do with the field. I decided to originally not implement it since it's mutable and only useful per repository. Maybe we can do something similar to pulp_ansible and add a new yanked content type that's presence in the repository tells us the content should be yanked. For now let's remove the field and deal with it later.
ed76616 to
fff96d2
Compare
546e0ad to
b0d5dc8
Compare
e113dee to
9b0c4b3
Compare
7812757 to
7916e65
Compare
closes #625