Closed nwehrman closed 1 year ago
Something to note: We do update declarations already. In this same example after upgrading to a newer version when you run a GET to pull down the declaration it adds "tsl1_3Enabled": false (default on newer versions that support it). However, we don't seem to remove the deprecated feature of SSLv2.
Thanks @nwehrman, in order to prioritize and understand the issue better, please reach out to us at automation_toolchain_pm@f5.com
We think it is not do-able at this moment and closing it. Sent more information to the customer.
Environment
Summary
In this scenario SSLv2 was deprecated in v14+. So if you upgrade from v13.x to 14.x+ then run a GET to the /declare endpoint to pull the declaration it will contain whatever was posted in v13 even if those objects are no longer configured on the device or valid. I'm using SSLv2 as an example but it's not uncommon for features to become deprecated on upgrade and AS3 should clean things up so that the declaration matches the device configuration.
Steps To Reproduce
Steps to reproduce the behavior:
Submit the following declaration on version 13.X
Run tmsh save sys config
Upgrade the device to 14.X or newer
Run GET to /declare endpoint
Observe that !SSLv2 still exists
However, !SSLv2 will NOT exist within the configuration or bigip.conf file
Attempts to POST this configuration again will fail because SSLv2 isn't valid in v14.X or newer ( ID 811333 cleans it up because it was removed)
Expected Behavior
AS3 declarations should function on the version they were requested from. Upgrading the configuration on the device shouldn't invalidate declarations without correcting them.
Actual Behavior
Attempts to re-use the declaration attained from the device will fail.