-
Notifications
You must be signed in to change notification settings - Fork 42
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
List signing services by type #779
Comments
The issue is that signing services are not master-detail like remotes et al.
and it looks like the pulp_href is the only discriminator today:
|
@mdellweg Do you think perhaps it would make sense to explicitly add a "type" field (or similar) to the AFAIK you can currently supply signing services of the wrong type to the API, and it will simply try to use it instead of providing a clear error message for that particular user error. Maybe the fact that there are signing services of very different types needs to be made much more explicit in general (not just for Pulp CLI)? |
I agree. I cannot recall the reasons why we didn't use the master-detail in the first place. |
Given the discussion, it seems CLI needs to wait for a pulpcore change to make this possible. Leaving this open for if/when/as such a thing happens. |
@mdellweg Do you think we should open a pulpcore issue? |
Is this still a thing? At that point, i think a type field in the pulpcore serializer together with an appropriate filter is in order. |
Summary
When using signing services it is essential to use the correct type of signing service.
Using
AsciiArmoredDetachedSigningService
where the plugin expectsAptReleaseSigningService
won't work.However, the
pulp signing-service
command does not appear to know a--type
option.Examples
I want to be able to do something like:
To list just the signing services of the specified type.
Challenges
I am not sure how problematic it is that
pulp signing-service
is a pulpcore associated command, while many signing service types may be plugin specific.The text was updated successfully, but these errors were encountered: