ok here's a fun one in case anyone else runs into it at a customer site -- if they have the Prism Central cluster named the same as the physical host cluster you're trying to actually deploy a UAG to, the script will fail trying to lookup the network - even though it seems to provide you with an API url that takes you to the network you were expecting ... if it's still sitting at the default "Unnamed" or named literally anything else other than one of the clusters you're trying to deploy to, it works just fine

for vis, because answer is in another channel, the response is using a name match and not looking at the function description we return, so it's always returning an array, and then matching against name which is still an array