dogtagpki

#800 REST API versioning
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

Currently API enhancements are done in backward compatible way by adding optional parameters or adding new methods. However, sometimes it's better to use separate API versions to allow greater flexibility while still maintaining backward compatibility.

Here's how other REST API's are versioned:
http://www.lexicalscope.com/blog/2012/03/12/how-are-rest-apis-versioned/

Design doc: http://pki.fedoraproject.org/wiki/API_Versioning

Based on the design the versioning will need to be implemented when there's a non-backward compatible change in the API. Until then the current API is considered version 1.0 and there is nothing needs to be changed for now.

Metadata Update from @edewata:
- Issue set to the milestone: 10.2 - 01/14 (January)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1367

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
Normal
defect
Rest interface
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.