Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Change-Id: I2314a2de3b9c2a1d9c2e5950659e44cb9bdda985
Signed-off-by: Sagar Srivastav <sagsriva@cisco.com>
|
|
- reader/initializer for pot
- pot read call in postman collection
Change-Id: I1e8f80449897c1ee5289f39eb7d75acb351eb255
Signed-off-by: Sagar Srivastav <sagsriva@cisco.com>
|
|
pot and trace customizers
-updated postman collection
Change-Id: Iebeebb1e12c52bf564e38b1cb65ce5425fc5fa22
Signed-off-by: Sagar Srivastav <sagsriva@cisco.com>
|