Last Modified: Jul 21, 2021
See more info
Known Affected Versions:
15.0.0, 15.0.1, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.1.1, 15.1.2, 22.214.171.124, 15.1.3, 126.96.36.199
Opened: Apr 16, 2019
When uploading a valid swagger file (OpenAPI version 2.0) to create an API Protection profile, the operation fails with an error message: info: [AccessDeployConfigWorker] Error in submitting transaction: Error: transaction failed:incomplete command.
The operation produces the error. This prevents the API Protection profile from being created using the swagger file, which is very inconvenient. This error also affects the AGC API Protection use case.
The swagger file contains quotation marks that are not escaped, e.g., the swagger file has description fields similar to the following examples. JSON: "description": "this quote \" will error" YAML: description: 'this quote " will error'
You can manually add the escape characters to the swagger file so that this error does not occur. Using the examples for JSON and YAML, this is how to fix them: JSON: "description": "this quote \\\" won't error" YAML: description: 'this quote \" won't error'