Infoblox support for vRA/vRO only valid for outdated/VMware unspported version 8.8.2

[#1]

One of the greatest things about vRA/vRO Aria Automation and Orchestration is it's integrations. But it is unfortunate when major companies can't support each other in this integration.

For example, did you know that the Infoblox provided IPAM plugins for vRA/vRO does not match the currently VMware supported versions of Aria Automation and Orchestration? Infoblox only supports up to version 8.8.2
https://docs.infoblox.com/space/ipamvmware8x/52593758/Deployment+Requirements

8.8.2 was End of Life for VMware (by Broadcom) as of July of 2023
End of General Support for VMware vRealize Automation 8.8.2 (94310)

https://kb.vmware.com/s/article/94310

Currently supported versions:
Build numbers and versions for VMware Aria Automation (formerly VMware vRealize Automation) (2143850)
https://kb.vmware.com/s/article/2143850

I have been using this plugin integration for years and hope to continue.

[#2]

This is in the works.

[#3]

How soon?  I am currently unable to get support on what appears to be a bug:

2024-01-22 12:31:13.215 -07:00info__item_stack:/item27
2024-01-22 12:31:13.226 -07:00info__item_stack:/item2
2024-01-22 12:31:13.237 -07:00info__item_stack:/item1
2024-01-22 12:31:13.241 -07:00infoSearching for IPAM connection with id [LOCAL-Gridmaster] ...
2024-01-22 12:31:13.243 -07:00infoThe IPAM connection with id [LOCAL-Gridmaster] was not found in the plugin cache.
2024-01-22 12:31:13.251 -07:00info__item_stack:/item8
2024-01-22 12:31:13.258 -07:00info__item_stack:/item19
2024-01-22 12:31:13.261 -07:00infoThe IPAM connection to add:
	id: LOCAL-Gridmaster
	hostName: gridmaster.local.edu
	apiType: WAPI
	priority: 1
	defaultNetworkView: null
	defaultDnsView: null
2024-01-22 12:31:13.267 -07:00info__item_stack:/item9
2024-01-22 12:31:13.275 -07:00info__item_stack:/item15
2024-01-22 12:31:13.277 -07:00infoChecking connectivity to the IPAM endpoint [gridmaster.local.edu/WAPI] ...
2024-01-22 12:31:13.282 -07:00info__item_stack:/item12
2024-01-22 12:31:13.312 -07:00warningAn error has occurred while checking connection with Infoblox IPAM server. Detail: SSL certificate error. (Workflow:Create IPAM connection / isConnectionOnline (item12)#4)
2024-01-22 12:31:13.319 -07:00info__item_stack:/item17
2024-01-22 12:31:13.322 -07:00infoConnection to the IPAM endpoint [gridmaster.local.edu/WAPI]: Failed
2024-01-22 12:31:13.340 -07:00info__item_stack:/item10
2024-01-22 12:31:13.359 -07:00info__item_stack:/item6
2024-01-22 12:31:13.378 -07:00errorWorkflow execution stack:
***
item: 'Create IPAM connection/item6', state: 'failed', business state: 'null', exception: 'Failed: Ipam Connection Failed. Check logs for more details. (Workflow:Create IPAM connection / Set output (item10)#2)'
workflow: 'Create IPAM connection' (ce57a2cd-fe8a-4f5a-a28f-6155d05301e8) 
|  'attribute': name=attrErrorCode type=string value=Failed: Ipam Connection Failed. Check logs for more details. (Workflow:Create IPAM connection / Set output (item10)#2)
|  'attribute': name=attrInputConnection type=InfobloxIPAM:IpamConnection value=dunes://service.dunes.ch/CustomSDKObject?id='LOCAL-Gridmaster'&dunesName='InfobloxIPAM:IpamConnection'
|  'attribute': name=attrCachedConnection type=InfobloxIPAM:IpamConnection value=__NULL__
|  'attribute': name=attrTestConnection type=InfobloxIPAM:IpamConnection value=dunes://service.dunes.ch/CustomSDKObject?id='LOCAL-Gridmaster'&dunesName='InfobloxIPAM:IpamConnection'
|  'attribute': name=attrSaveConnection type=string value=
|  'attribute': name=attrRefreshSslContext type=boolean value=true
|  'input': name=id type=string value=LOCAL-Gridmaster
|  'input': name=url type=string value=https://gridmaster.local.edu
|  'input': name=username type=string value=myvrauser
|  'input': name=password type=SecureString value=__NULL__
|  'input': name=priority type=number value=1.0
|  'input': name=apiType type=InfobloxIPAM:IpamApiType value=dunes://service.dunes.ch/CustomSDKObject?id='WAPI'&dunesName='InfobloxIPAM:IpamApiType'
|  'output': name=ipamConnectionOut type=InfobloxIPAM:IpamConnection value=null
*** End of execution stack.

From the local vRO member node, using the connection string with curl, gridmaster.local.edu/WAPI fails.  But I can connect using the connection string gridmaster.local.edu/wapi.  But Infoblox support won't even look at this since I am at vRA 8.10.1. 

Sales team reports 2 quarters, or half a year.  I need to roll this project out this month.

[#4]

RFE-13191 is targeting vRA / vRO 8.11.X, 8.12 is planned for a later NIOS release. We are expecting this to be delivered in the summer, so yes 2 quarters.

[#5]

---

@Layer8 wrote:

RFE-13191 is targeting vRA / vRO 8.11.X, 8.12 is planned for a later NIOS release. We are expecting this to be delivered in the summer, so yes 2 quarters.

---

Just in time for VMware to stop supporting those versions.  This is unacceptable

Product Name	SaaS Monthly Release	On-Prem Release Date	On-Prem Build # -Version	On-Prem Installer Build # - Version	On-Prem End of General Support
Aria Automation 8.14.1	November 2023	2023-11-28	22830382 - 8.14.1.33478	22857517 - 1.0.0.1593	2024-11-28
Aria Automation 8.14	October 2023	2023-10-19	22618990 - 8.14.0.33079	22630473 - 1.0.0.1580	2024-10-19
Aria Automation 8.13.1	August 2023	2023-09-07	22360938 - 8.13.1.32340	22395538 - 1.0.0.1545	2024-09-07
Aria Automation 8.13	July 2023	2023-08-03	22178981 - 8.13.0.31759	22191255 - 1.0.0.1519	2024-08-03
Aria Automation 8.12.2	June 2023	2023-06-29	21949837 - 8.12.2.31329	22003350 - 1.0.0.1513	2024-06-29
Aria Automation 8.12.1	May 2023	2023-05-18	21768489 - 8.12.1.31050	N/A	2024-05-18
Aria Automation 8.12	April 2023	2023-04-20	21622235 - 8.12.0.30728	21628956 - 1.0.0.1488	2024-04-20
vRealize Automation 8.11.2	March 2023	2023-03-21	21452955 - 8.11.2.30052	21471040 - 1.0.0.1447	2024-03-16
vRealize Automation 8.11.1	February 2023	2023-02-21	21309636 - 8.11.1.29538	21329473 - 1.0.0.1420	2024-02-21
vRealize Automation 8.11	December 2022	2023-01-19	21128101 - 8.11.0.27829	N/A	2024-01-19

[#6]

In some cases there are large changes to the formats and content of the APIs between versions, which are relased nearly monthly... not exactly an easy target to hit. 

Infoblox intentionally do not deprecate API calls, for this exact reason. Yes, we release new ones for optimization, and with hotfixes we can kill vulnerable ones... but asking a vendor to support a monthly cadence for a free feature/integration is a big ask. This model causes attrition to vendors as it's a way to create a walled garden, and 'use our internal tool for that' etc.

However, we are under new leadership and aligning a new cloud strategy... including in some cases paying OEMs to build their integrations to our products. I'm unsure of VMWare's status in this hierarchy currently, but it is something we are aware of and are taking larger steps beyond just "hire more developers to do this thing" type deal. 

[#7]

I can understand not being able keep up.  But being told by Infoblox support that this was an "Unsupported Version" as a copout reason to close the support request, especially when shown that the issue was case sensitivity call between the Infoblox provided plug-in and the Infoblox provided version of NIOS is what is unacceptable.  "WAP"I vs "wapi" via curl. 

---

@Layer8 wrote:

In some cases there are large changes to the formats and content of the APIs between versions, which are relased nearly monthly... not exactly an easy target to hit. 

Infoblox intentionally do not deprecate API calls, for this exact reason. Yes, we release new ones for optimization, and with hotfixes we can kill vulnerable ones... but asking a vendor to support a monthly cadence for a free feature/integration is a big ask. This model causes attrition to vendors as it's a way to create a walled garden, and 'use our internal tool for that' etc.

However, we are under new leadership and aligning a new cloud strategy... including in some cases paying OEMs to build their integrations to our products. I'm unsure of VMWare's status in this hierarchy currently, but it is something we are aware of and are taking larger steps beyond just "hire more developers to do this thing" type deal. 

---

[#8]

I understand. I think the efforts required to 'support' something is a very involved process. We are talking about training, testing, instructors, and certification for hundreds of people on a rolling timeframe for something that does not return revenue to the business. Although that seems an easy fix, the knowledge required to be able to identify typeError issues in WAPI calls isn't your standard L3 tech always IMO. 

[#9]

So do we have an update when the typeError will be resolved?   Aria Automation / Orchestrator 8.16.2 is out now. 

[#10]

Have you enrolled in EAP? Gives you a direct ear to PM to get the answers from the horse's mouth.

Just checked that JIRA Issue, there are related ones as well (IPAM plugins, etc.) that are all 'planned for' 9.0.4 and 9.0.5. The former is imminent and the latter is likely this calendar year. 

However, I am not seeing in the Jira workflow builder that it's actually marked resolved in a new issue. Did your account SA talk about getting field prioritization?