Forum Discussion
Nimbostratusstrict updates in iapp
re: enable(disable) strict updates in iapps
A few questions;
- How can I (or can it be done) code "disable strict updates" in the implementation section of an iApp template? Assuming this can be done, I'm sure there are caveats.
- If I can disable, does this remove the ability to "completely" remove the application service later by issuing a command
tmsh delete sys application service fred.app/fred
I have tested the code, which does appear to work, but wanted to know if there are any functional issues (gotcha's) I need to be aware of.
Thanks
2 Replies
Sam_HallDon't know about number 1.
While I don't fully understand the inner workings for question number 2, I've seen instances where additional configuration added within /Common/fred.app that somehow came to be - though are not part of the iApp, cannot be removed by attempting to delete the iApp. Then you have to hunt them down in bigip.conf and remove them manually. It's a royal pain. It would be nice if there was a purge option or something that just forcibly removes anything found to be left within the iApp directory.
If all you want to do is change a setting here or there, it's should be fine. Personally, I like to keep my iApps clean and reconfigurable at any time. It's certainly better to enhance or branch the template with additional features (if time permits).
The tmsh command you are looking for is:
modify sys application service fred.app/fred strict-updates disabled
Disabling strictness will not effect your ability to delete the iapp at a later date, however, if you use profiles that are outside of the iapp (since strictness is off you can do this) and the profile is being used elsewhere, you will see an error indicating the profile can not be deleted because it is in use when you try to delete the iApp.
