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
Allow uploads to be used with NoArtifactContentUploadSerializer #4348
Comments
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Sep 1, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Sep 1, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Sep 1, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Sep 1, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Sep 6, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 6, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 6, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 6, 2023
mdellweg
added a commit
that referenced
this issue
Oct 12, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 13, 2023
This turned out to be a breaking change. It got reverted and postponed to 3.40. |
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 13, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 17, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 27, 2023
mdellweg
added a commit
to mdellweg/pulpcore
that referenced
this issue
Oct 30, 2023
mdellweg
added a commit
that referenced
this issue
Oct 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we allow artifact, file or upload to create single artifact content, but only file for no-artifact content.
This should allow to specify an upload to be used by both content serializers on creation.
The text was updated successfully, but these errors were encountered: