BIG-IP Next Automation: AS3 Basics
I need a little Mr. Miyagi right now to grab my face and intently look me in the eye and give me a "Concentrate! Focus power!" For those of you youngins' who don't know who that is, he's the OG Karat...
Updated Jun 28, 2024
Version 3.0
JRahm
Admin
Admin
Juergen_Mang
MVP
MVPThanks for this article. I tested it and it works as you described.
One thing I find impractical is that I can't post the declaration a second time to update it. This makes automation workflows unnecessarily complicated. Or is there any trick to make it simple?
One other question that I have, after reading this article
"target": "<BIG-IP Next Instance IP Address>"
What is the target, if I have a cluster?
JRahmAdmin
AdminIf using the compatibility API re-POSTing the declaration should work to make an update. If using the documents API, you need to send a PUT to make an update.
In Next, an HA cluster is regarded as a single instance functionally, so you would target the management plane floating IP address.
- Juergen_Mang
In Next, an HA cluster is regarded as a single instance functionally, so you would target the management plane floating IP address.
Management floating IP - great! I should really setup a Next cluster to get more familiar with it.
If using the compatibility API re-POSTing the declaration should work to make an update. If using the documents API, you need to send a PUT to make an update.
Ok, I used the new API. Is the compatibility API came to stay? Or should it be used only for easier transistions? I thought it is more future proof to use the new API's.