DO deploy breaks between 1.36 and 1.37

[rhavenn]

I was sent over here by F5 support since there is no category to select "DO" support in the F5 support page and the technician seemed unwilling to troubleshoot the issue even though we have a valid support contract.

We're deploying to Azure F5 "best" instances and stuff that was working last week stops working when moving from 1.36.0 / 1.36.1 -> 1.37.0 of the DO extension. Rolling back and it works fine again. There aren't any documented changes I see that would impact us.

DO: 1.36.0 / 1.36.1 / 1.37.0 BIGIP: 17.1

Using ansible and jinja templates to cobble together a JSON. Pulling the JSON out via -vvvv flags or from the DO "poll" command to get the status and running it through the "latest" schema check shows no errors outside of our tacacs secret not being included in the polled version. Putting that back in and it passes validation as per: https://clouddocs.f5.com/products/extensions/f5-declarative-onboarding/latest/validate.html

The error message is unhelpful: invalid config - rolled back","errors":["one or more properties must be specified","one or more properties must be specified"]

but there isn't even any info as to a line number or even a Class to go off of to narrow down the issue and which schema Class I should be looking at in more detail. No actual changes were made on the JSON template side. It works on 1.36.1 and doesn't work on 1.37.0 .

I can post our JSON to the F5 support ticket we have open if you would like, but I would prefer to not post it here.

[mdditt2000]

@rhavenn please can you review the Behavioral Changes coming to Declarative Onboarding 1.36

This video demonstrates the behavioral changes coming to Declarative Onboarding 1.36. The default value for 'allowService' on a 'SelfIp' will change from 'default' to 'none'

GitHub https://github.com/mdditt2000/f5-declarative-onboarding/tree/main/user-guides/behavioral-changes#readme Demo https://youtu.be/_0DiUfOr6u0

This should resolve your issue.