Class: L4_Profile - idleTimeout range missing zero or "immediate" value #929
Description
Environment
- Application Services Version: 3.46.0
- BIG-IP Version: 17.1.2
Summary
Converting via Chariot the idleTime out value is set to "immediate" via the UI setting a zero.
This is not an acceptable value in AS3 the range is -1,1 to infinity.
Customer leveraging AS3 for automation, this is not aligned with the possible values the UI accepts. Chariot in VSCode generates the correct output of "immediate" which is reflected in the tmsh CLI output.
Steps To Reproduce
Steps to reproduce the behavior:
- Submit the following declaration:
"custom_fastl4_ipv6_mss": {
"remark": "none",
**"idleTimeout": "immediate",**
"keepAliveInterval": 0,
"looseClose": true,
"looseInitialization": true,
"maxSegmentSize": 1400,
"resetOnTimeout": false,
"synCookieEnable": false,
"synCookieAllowlist": false,
"tcpCloseTimeout": 5,
"tcpHandshakeTimeout": 5,
"class": "L4_Profile"
},- Observe the following error response:
Per Chariot conversion from VSCode with "immediate":
{
"id": "e24324a4-12f5-4698-99bd-54eafa486b08",
"results": [
{
"code": 422,
"errors": [
"/Common/Shared/custom_fastl4_ipv4_mss/idleTimeout: should be integer"
],
"declarationFullId": "",
"message": "declaration is invalid"
}
],
"declaration": {}
}Update to reflect the UI value of "0":
{
"id": "a27a05b2-a817-4e2b-b4e1-9ed69c0bc0b6",
"results": [
{
"code": 422,
"errors": [
"/Common/Shared/custom_fastl4_ipv4_mss/idleTimeout: should be >= 1"
],
"declarationFullId": "",
"message": "declaration is invalid"
}
],
"declaration": {}
}Expected Behavior
Expectation is the value of "0" or "immediate" to be accepted per the UI acceptable value range.
Actual Behavior
Value needs to be manually modified to "1" as "0" or "immediate" are not accepted per the schema docs and the parser.