Users have requested the ability to use SSH to configure the F5 Modules for Ansible.
To get the same results as the existing
Parameter classes, you can try to use local
curl commands to parse the REST output.
Before you use this method, note the following limitations.
Only two roles can use the “Advanced shell,” also known as “bash.”
If you have either role, you can use
curl through the
tmsh run util bash command.
All other roles are limited to the
tmsh shell only. In
tmsh, you do not natively have a
curl command you can use.
Appliance mode’s restrictions are outlined in this support article:
Some of the restrictions are:
bash) has been removed.
bpsh), and Traffic Management Shell (
These restrictions make it difficult to configure the device by using an API that provides structured data.
In addition, some of the actions the modules take become impossible. For example, in Appliance Mode, you cannot upload file data that would require SCP functionality.
As it stands, these requirements mean that you would need to rely on
tmsh itself to accomplish your tasks.
This means working with a tool that provides free-form output, rather than structured output.
There is a
--oneline argument that may be supplied to
tmsh commands, but it is not clear how parseable, or reliable, this format is.
For the above reasons, if you pursue CLI functionality for any of these modules, F5 recommends that the functionality be allowed for users with one of the following roles only:
These roles can access all modules.
Without making this a requirement, it may not be possible to provide you with a reliable way to configure the system, due to restrictions put in place by other roles.