For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Getting Started with the f5-common-python SDK

If you have dabbled with python and iControl over the years, you might be familiar with some of my other “Getting Stared with …” articles on python libraries. I started my last, on Bigsuds, this way:...
Updated Jun 06, 2023
Version 2.0
devops
f5-common-python
iControlREST
python
JRahm's avatar
Icon for Admin rankAdmin
Christ Follower, Husband, Father, Technologist. I love community and I especially love THIS community. My background is networking, but I've dabbled in all the F5 iStuff, I'm a recovering Perl guy, and am very much a python enthusiast. Learning alongside all of you in this accelerating industry toward modern apps and architectures.
View Profile
F5_Digger_13600's avatar
F5_Digger_13600
Icon for Cirrus rankCirrus
Oct 03, 2017

yes Jason.

 

 

With partition='Common' parameter, .exists() call works as expected.

 

Now it brought me up another question. How do I know if I need to specify additional parameter like partition='xxx' parameter for exist() call to works?

 

 

Based on my test, I didn't need to specify partition='xxx' parameter for exists() and it worked. For example, most of protocol profile resources; http, tcp, udp, http and persistence profile resources; source, destination, hash persistence )

 

didn't require any additional parameters like partition='xxx'.

 

One exception so far I found was the exists() of Local traffic policy profile resource which requires two additional parameter (partition='xxx' and subPath='xxx') as well as name='xxx'.

 

 

Do you know any easy way of figuring out required parameters of each methods call (Create(), Refresh(), Update(), Delete(), Load(), Exists())?