Nailgun REST API versioning
Registered by
Nikolay Markov
Storing objects in the database as JSON blobs causes a lot of implicit changes to the API. It breaks time-to-time our clients (python-fuelclient, nailgun-agent, fuel-qa, etc). In order to prevent breaking of Nailgun clients, we must introduce versioned API.
Moreover, having versioned API is the only way to introduce major changes to it when they are needed. So far we're driven by keeping somehow backward compatibility, but sometime we really need to redesign API endpoint in order to provide better user experience.
Blueprint information
- Status:
- Not started
- Approver:
- Ihor Kalnytskyi
- Priority:
- Undefined
- Drafter:
- Fuel Python (Deprecated)
- Direction:
- Needs approval
- Assignee:
- Fuel Python (Deprecated)
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
-
next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
