Project

Profile

Help

Issue #9563

It should not be necessary to provide the base url to utilize a AptReleaseSigningService

Added by jxsxs 27 days ago. Updated 13 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Using a AsciiArmoredDetachedSigningService it suffices to provide the pulp_href whilst the AptReleaseSigningService wants you to provide the full path.

i.e. http://yourpulphost.com/{pulp_href}

It's relatively hard to pin the base_path when having multiple environments. It would be really great if we only have to pass the pulp_href.

History

#1 Updated by jxsxs 15 days ago

Any news here quba42?

#2 Updated by quba42 15 days ago

I had a look at how pulp_deb and pulp_rpm use signing services and noticed the following:

The AptPublicationSerializer uses the following field relation in pulp_deb/app/serializers/publication_serializers.py:

    signing_service = HyperlinkedRelatedField(
        help_text="Sign Release files with this signing key",
        many=False,
        queryset=AptReleaseSigningService.objects.all(),
        view_name="signing-services-detail",
        required=False,
    )

The corresponding RPM serializer uses just RelatedField instead of HyperlinkedRelatedField.

I suspect this is the root cause of the bug, but I have not yet had a chance to test it.

#3 Updated by jxsxs 13 days ago

That indeed sounds like a good candidate..

Please register to edit this issue

Also available in: Atom PDF