Story #1597
closed
As a user, I can turn v2 sync off
100%
Description
In order for users to migrate to pulp_docker 2.0, they will need to keep their v1 repositories. If those repos have a docker hub feed, the feed may respond to the /v2/ endpoint causing pulp to incorrectly trigger v2 sync. To prevent this,there should be a configurable option, `enable_v2` that should default to true but should be turned off for users that are migrating v1 repos.
Related issues
Updated by amacdona@redhat.com about 8 years ago
- Related to Issue #1598: clarify docs that index.docker.io only supported for v1 added
Updated by jortel@redhat.com about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
- Groomed changed from No to Yes
- Tags Easy Fix added
Added by jortel@redhat.com about 8 years ago
Added by jortel@redhat.com about 8 years ago
Revision adb35e2c | View on GitHub
Support v2 enabled importer configuration property. closes #1597
Added by jortel@redhat.com about 8 years ago
Revision adb35e2c | View on GitHub
Support v2 enabled importer configuration property. closes #1597
Added by jortel@redhat.com about 8 years ago
Revision adb35e2c | View on GitHub
Support v2 enabled importer configuration property. closes #1597
Updated by jortel@redhat.com about 8 years ago
Updated by jortel@redhat.com about 8 years ago
- Status changed from ASSIGNED to POST
Updated by jortel@redhat.com about 8 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset adb35e2c13b9b0477379ced9c27f082ebd0e895e.
Updated by dkliban@redhat.com about 8 years ago
- Status changed from MODIFIED to 5
Updated by semyers almost 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
.
Support v2 enabled importer configuration property. closes #1597