Refactor #4593
closed
rename certguard type to x509
Status:
CLOSED - CURRENTRELEASE
Description
IMO the call to make a new x509 certguard would make more sense if it was:
http://localhost:8000/pulp/api/v3/contentguards/certguard/x509/
instead of
http://localhost:8000/pulp/api/v3/contentguards/certguard/certguard/
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Sprint set to Sprint 51
+1 to this story @asmacdo.
- Groomed changed from No to Yes
- Subject changed from rename certguard type to x509 to rename certguard type to X.509
- Description updated (diff)
Switchiing to its formal name: X.509
- Subject changed from rename certguard type to X.509 to rename certguard type to x509
- Description updated (diff)
Actually openssl uses this shorthand so I'll use it too.
- Status changed from ASSIGNED to POST
- Description updated (diff)
This PR is ready, but the problem with the URL that ends in 'certguard/x509/' is that it still reserves the model TYPE as 'certguard' when really that is x509 also. This means the sane URL to use (and not occupy the generic term certguard correctly) is 'x509/x509'. Overall the master detail URL structure I think is causing this to not be as awesome, but I believe 'x509/x509' is better than 'certguard/certguard' so I'm +1 to this change.
Rewriting description because of it.
- Description updated (diff)
Actually the name is not determined by the TYPE, it's the app name so it will be certguard/x509 which is great.
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 1.0.0 Release
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Updates x509 certguard URL
The name being x509 makes more sense than certguard.
https://pulp.plan.io/issues/4593 closes #4593