Skip to content
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

Add retrieve function to all relevant serializers #1010

Closed
quba42 opened this issue Feb 12, 2024 · 0 comments · Fixed by #1018
Closed

Add retrieve function to all relevant serializers #1010

quba42 opened this issue Feb 12, 2024 · 0 comments · Fixed by #1018
Labels
.feature CHANGES/<issue_number>.feature .removal CHANGES/<issue_number>.removal

Comments

@quba42
Copy link
Collaborator

quba42 commented Feb 12, 2024

Is your feature request related to a problem? Please describe.
We currently have retrieve functions for the BasePackageSerializer and the GenericContentSerializer.

Describe the solution you'd like
We should add retrieve functionality to all content API endpoints.

Additional context
This changes API behavior and so is a breaking change. We should add a relevant removal changelog entry!

@quba42 quba42 added .feature CHANGES/<issue_number>.feature .removal CHANGES/<issue_number>.removal labels Feb 12, 2024
@quba42 quba42 linked a pull request Feb 27, 2024 that will close this issue
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Feb 28, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Feb 29, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Feb 29, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
quba42 added a commit to ATIX-AG/pulp_deb that referenced this issue Mar 4, 2024
closes pulp#1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.
hstct pushed a commit that referenced this issue Apr 11, 2024
closes #1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.

(cherry picked from commit 599104f)
hstct pushed a commit that referenced this issue Apr 11, 2024
closes #1010

In particular we are adding the new behaviour for:

- ReleaseArchitecture
- ReleaseComponent

but deliberately not for PackageReleaseComponent, which should only be
created indirectly using package actions.

(cherry picked from commit 599104f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.feature CHANGES/<issue_number>.feature .removal CHANGES/<issue_number>.removal
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant