Story #4669
closed
As a user, I can associate a RepositoryVersion with a DockerDistribution
Added by dkliban@redhat.com about 5 years ago. Updated about 4 years ago.
100%
Description
The docker plugin currently requires the user to create a Publication before the content of the RepositoryVersion can be made available via a Distribution. The is no publisher that would generate metadata for the content, so the Publication and RepositoryVersion are exactly the same. The creation of a Publication is unnecessary steps. The user should be able to create a Distribution with a reference to a RepositoryVersion.
Related issues
Updated by amacdona@redhat.com about 5 years ago
- Blocks Task #4671: Publish REST API on read the docs added
Updated by amacdona@redhat.com about 5 years ago
- Blocks deleted (Task #4671: Publish REST API on read the docs )
Updated by ipanova@redhat.com about 5 years ago
- Groomed changed from No to Yes
- Sprint set to Sprint 51
Updated by dkliban@redhat.com about 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Added by dkliban@redhat.com about 5 years ago
Updated by dkliban@redhat.com about 5 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com about 5 years ago
Revision 202d3cdf | View on GitHub
Problem: Publications are not needed for Docker plugin
Solution: Add 'repository_version' field to DockerDistribution
This patch allows users to create DockerDistributions that serve repository versions. A distribution can be created with either a repository or repository version defined. If a repository is defined, the latest version of that repository is always available at the distribution. If a repository version is specified, then that repository version is always available at that distribution.
This patch updates an existing test and adds a new one. The two tests assert that a docker or podman pull can be performed when a repository is used in a distribution and when a repository version is used.
This patch also fixes the tests to work with docker as the client.
Added by dkliban@redhat.com about 5 years ago
Revision 202d3cdf | View on GitHub
Problem: Publications are not needed for Docker plugin
Solution: Add 'repository_version' field to DockerDistribution
This patch allows users to create DockerDistributions that serve repository versions. A distribution can be created with either a repository or repository version defined. If a repository is defined, the latest version of that repository is always available at the distribution. If a repository version is specified, then that repository version is always available at that distribution.
This patch updates an existing test and adds a new one. The two tests assert that a docker or podman pull can be performed when a repository is used in a distribution and when a repository version is used.
This patch also fixes the tests to work with docker as the client.
Added by dkliban@redhat.com about 5 years ago
Revision 202d3cdf | View on GitHub
Problem: Publications are not needed for Docker plugin
Solution: Add 'repository_version' field to DockerDistribution
This patch allows users to create DockerDistributions that serve repository versions. A distribution can be created with either a repository or repository version defined. If a repository is defined, the latest version of that repository is always available at the distribution. If a repository version is specified, then that repository version is always available at that distribution.
This patch updates an existing test and adds a new one. The two tests assert that a docker or podman pull can be performed when a repository is used in a distribution and when a repository version is used.
This patch also fixes the tests to work with docker as the client.
Added by dkliban@redhat.com about 5 years ago
Revision 202d3cdf | View on GitHub
Problem: Publications are not needed for Docker plugin
Solution: Add 'repository_version' field to DockerDistribution
This patch allows users to create DockerDistributions that serve repository versions. A distribution can be created with either a repository or repository version defined. If a repository is defined, the latest version of that repository is always available at the distribution. If a repository version is specified, then that repository version is always available at that distribution.
This patch updates an existing test and adds a new one. The two tests assert that a docker or podman pull can be performed when a repository is used in a distribution and when a repository version is used.
This patch also fixes the tests to work with docker as the client.
Updated by dkliban@redhat.com about 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset commit:pulp_docker|202d3cdffa6f9707b9f84c569b1a8f78a37dc940.
Updated by kersom almost 5 years ago
- Related to Test #4754: As a user, I can associate a RepositoryVersion with a DockerDistribution added
Updated by ipanova@redhat.com over 4 years ago
- Project changed from Docker Support to Container Support
Updated by ipanova@redhat.com over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Problem: BaseDistribution.validate() is too Distribution specific
Solution: Move validate() to the Distribution instead
This patch allows classes that inherit from BaseDistribution to call super().validate(data) to get the validation provided by the ModelSerializer.
This patch also removes base_path from BaseDistribution because it is defined on the Distribution. DockerDistribution also defines it for itself.
re: #4669 https://pulp.plan.io/issues/4669