30ed3064ab
The V2.1 API implementation does not have a 1-1 mapping of extensions compared to the V2 API. For example because many of the dummy extensions were only originally added in order to be able to signal to the API clients that new functionality was available these were not ported and functionally hard coded into the original plugin. However in order to retain complete backwards compatibility we need to have an /extensions output which is identical to the original V2 API. This patch implements that backwards compatibility including fields such as XML namespaces, links and updated which are no longer supported. Some minor testcase changes to reflect no real xml support in v2.1 now Part of blueprint v2-on-v3-api Change-Id: I8e63a684093dfe3a643c07b20e8080c1e950ed5a |
||
|---|---|---|
| .. | ||
| extensions-get-resp.json | ||