Closed samualblair closed 6 months ago
Thanks Michel, This a very detailed and helpful description for that bug, & I'll use the provided examples within the unit testing.
The fix is already in-place within the wasm portal https://ipvx.me/f5
The python lib requires a bit of work & will include the same fix as well.
Thank you! I didn't expect such quick response or resolution, very much appreciated! Yes, I can confirm it looks to be working great in the wasm portal now!
The fix is now pushed to pypi with release v 0.3.0
I'm sure there are other edge cases but I have found when persist profile is present some data is not processed for a virtual server. (tested with the wasm module version)
Two virtual server configurations with the only significant difference being the persist profile, you can see the failure. Doesn't crash or throw any error, but fails to record much of the other relevant information.
I assume processing just halts for for variables related to that object, as the location of the 'persist' statement does affect the output.
When the persist statement is in the default location from the config file (middle of the config), as seen in EXAMPLE_VS_FAIL Here i see the following was lost:
When the persist statement is in the bottom of the config file as seen in EXAMPLE_VS_FAIL2 Here i see the only thing lost was the persist profile. Unfortunately this is only an example, in the normal config output this is not the location of the persistence profile.
Example:
Which translates to this