Move JSON schemas into the separate repo/library
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Wishlist
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Wishlist
|
Fuel Python (Deprecated) | ||
Newton |
Confirmed
|
Wishlist
|
Fuel Sustaining |
Bug Description
There are several places where similar schema is required like fuel-web, fuel-plugins, python-fuelclient and so on. Currently there is not other way to share schemas than making cross-project dependancies and importing one project from another or copy-paste schema definition from one project to another that is the worst way.
Also sometimes its desirable to settle integration API and data format before endpoints implementation start.
In the light of Nailgun modularisation data schema management could became more sensitive area than now.
So, i purpose to take JSON schemas as well as any other API and data interexchange formats descriptions to the distinct library/repository to make easier:
1. modification
2. usage
3. versioning
4. API discussion
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: tech-debt |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |