Components list of a deployed iApp is incorrect and way too short

Turning off strict-updates quickly makes a mess of things. This article may help you to understand the consequences: https://devcentral.f5.com/s/articles/understanding-iapps-18224. That said, if you are sophistocated enough to do that kind of work, then you can add the app-service tag to almost any LTM object to include it in the component view. As noted in the article, mark & sweep will delete that object if you re-run the iApp, so be aware of what you are doing.

Thanks, I read the article, and it seems that I shouldn't disable Strict Updates so much. It's never my plan, till the app managers want exceptions for one specific VS :)

 

If I understand correctly, reconfiguring an iApp is like performing a live upgrade. Things that stay the same just stay that way, the VS stays live etc.

 

Now... is there a way (a tmsh command perhaps) that performs a delete of all iApp generated config, and regenerates? Service interruptions are not a problem. So the same effect as deleting an iApp and associated config, and creating a new one with the same inputs.

 

I know a tmsh command that reconfigures an iApp, but as is said in your article, it isn't garantueed that all "bad"/manually changed settings are reset/overwritten. So to be absolutely sure that all settings are now as they should be, from a virgin deployment, for a messy iApp that had Strict Updates disabled?