Using Bash/cURL to create a new Integration Gateway path using POST via the API results in meta values not being applied (although /api/docs sample payload shows meta for the POST request). However, extracting the new routeID from the API response and sending a new PUT request with the same payload causes the meta values to apply correctly.
Expected Behavior
Meta values should apply in first step when new route is created.
Steps To Reproduce
New Route Payload:
{
"endpoint": "/simpleTest",
"method": "POST",
"enabled": false,
"meta": {
"debug": true,
"async": false,
"description": "This is a description."
}
}
cURL Command (URI and data-raw omitted; API token obtained and auth header generated separately):
Is there an existing issue for this?
Version of Corteza
2023.3.8
Current Behavior
Using Bash/cURL to create a new Integration Gateway path using POST via the API results in meta values not being applied (although /api/docs sample payload shows meta for the POST request). However, extracting the new routeID from the API response and sending a new PUT request with the same payload causes the meta values to apply correctly.
Expected Behavior
Meta values should apply in first step when new route is created.
Steps To Reproduce
New Route Payload:
cURL Command (URI and data-raw omitted; API token obtained and auth header generated separately):
Response (identifiers omitted):
Subsequent PUT request successfully applies meta values:
Environment and versions
No response
Anything else?
Known workaround:
api/system/apigw/route/{routeID}