summaryrefslogtreecommitdiffstats
path: root/lisp/gpe_postman_collection.json
AgeCommit message (Collapse)AuthorFilesLines
2018-06-01HC2VPP-339: convert postman collections to v2.1.0 formatMarek Gradzki1-305/+432
Mantaining postman collections in v1 format is difficult due to UID strings. Postman collection v2 fixes the issue and many others, see http://blog.getpostman.com/2015/06/05/travelogue-of-postman-collection-format-v2/ Collections in v1 format, were converted using postman-collection-transformer. Output was transformed using JSON.stringify with space='\t', to be compliant with Postman application which does not support spaces for indentation. Coverted collections were tested using Postman v6.1.3. Previous version of postman collections were renamed to *_v1.0.0.json or *_v2.0.0.json. Removal is planned in 18.10 (HC2VPP-338). Change-Id: I6caf496293fccc1f9aadcdece668b5200fe07122 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
2017-08-07HC2VPP-162 - use composite key for locator pairJan Srnicek1-1/+1
Removes need for custom mapping for locator pairs and their ids Change-Id: Idaa6ee5ec74d8bf57a72bea95c0c0d408e6e940e Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>
2017-06-19HC2VPP-168 - Gpe native entries support(write only)Jan Srnicek1-79/+219
requires https://gerrit.fd.io/r/#/c/7168 to be merged Change-Id: I5b734af662e651df5753f64f14b6b44d863ecbe8 Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>
2017-05-24HC2VPP-147 - Gpe entry implementationJan Srnicek1-0/+200
Change-Id: Ie7887c8e8f10678410ad677c425bfed1690bf440 Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>