#4427 [RFE] New API versioning
Closed: Fixed None Opened 5 years ago by mbasti.

Current API versioning can cause conflicts.

If we increase version in ipa-3-3 branch to version which hits ipa-4 capability, it could break communication between ipa-3 clients and ipa-4 servers

We need change versioning, to support API changes in bugfix releases

Triaged today, from pviktori's POV, it would make sense to do it in 4.1, in case we want to backport a capability from 4.1 to 4.0.

Moving to 4.1 as a stretch goal.

This was not developed in 4.1 time frame, moving out.

Processing leftovers from 4.2 backlog - this ticket was found as suitable for consideration in next big feature release - 4.4.

4.4 Priority

The design page needs extending or split. Now related also to #4739


  • 9a21964 misc: generate plugins result directly in the command
  • 79d1f58 plugable: use plugin class as the key in API namespaces
  • 4284d4f plugable: support plugin versioning
  • 8466e94 schema: support plugin versioning
  • 5f52e0f frontend: forward command calls using full name

Support for new version of command was implemented, marking as fixed.

Metadata Update from @mbasti:
- Issue assigned to jcholast
- Issue set to the milestone: FreeIPA 4.4

3 years ago

Login to comment on this ticket.