tmsh2iapp iApp generator // automate in minutes with easily generated iApps
Problem this snippet solves:
Advantages of using iApps for automation instead of plain ansible, plain REST calls, etc...
When deploying configurations as iApps the configurations are sel...
Published Jul 25, 2017
Version 1.0
New feature release
Like any other iApp, the iApps created by tmsh2iapp can be deployed in any partition. By default iApp's objects are created in the //. This allows having several instances of the same iApp in the same partition.
I had a request of optionally implementing a different behavior. The next two features allow iApp's objects to be created by default in /. In other words: without a per-iApp folder. Therefore when using this option it will not be possible to create two instances of the same iApp in the same partition but several instances in several partitions will be still possible.
Features:
- Implemented "nofolder" and "nofolder-disable-strict-updates" options
- Implemented @partition variable for some corner cases of iApps created with "nofolder" options