-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop supporting manifests with artifacts and enforce the data migration #1621
Labels
Comments
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
May 23, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
May 23, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 2, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 2, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 2, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 2, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 3, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 3, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 18, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
MichalPysik
added a commit
to MichalPysik/pulp_container
that referenced
this issue
Jun 18, 2024
This commit removes support for manifests storing their data inside an artifact instead of using the recently introduced Manifest.data text field. closes pulp#1621
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In one of the upcoming releases (2.22+), we would like to remove the backward compatible code which can handle both artifactless manifests and manifests with artifacts. We want to deal only with artifactless manifests and enforce the migration.
Furthermore, it does make sense to revisit the redirect to content-app/object-storage from api-app because we can return
manifest.data
immediately from api-app.The relevant code paths are annotated with:
The text was updated successfully, but these errors were encountered: