The Dynamic Types plug-in available with vRealize Orchestrator gives considerable flexibility to what you wish to offer "as a Service" via vRealize Automation. Christophe has released a Dynamic Types plug-in generator package that helps simplify the creation of a Dynamic Types plug-in for HTTP-REST services. He's also provided an NSX-v Dynamic Types plug-in using this technology. The plug-in attached here is intended to help map database tables to vRO so that you may easily request table records as a service.
NOTE/WARNING: This package was developed and tested with a Microsoft SQL Server. As such, the query in the action "com.vmware.coe.sql.getTableColumnNames" is likely to only work with a SQL Server. If you are using PostgreSQL, MySQL, or Oracle, you will likely need to modify the first line of this action to reflect the proper syntax of retrieving a record.
This is my first Dynamic Types plug-in generator package so please do provide feedback
The package was developed for use with a series of articles on my blog. As I work through the series, I'll add links here:
- SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 1
- SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 2
- SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 3
What does the attached package do?
The package attached here will quickly build out an inventory based on a SQL Plug-in Database Table
General Instructions are below: (For more detailed instructions, please view the articles linked above)
- Import the package to your vRO server
- Have one or more Databases setup in the SQL plug-in
- Run the "1 - Define Plug-in Namespace and DB" workflow
- Run the "2 - Define a Type and its parent folder" workflow
- Refresh your vRO Inventory and confirm the table you mapped now shows as a folder under your namespace and records in that table show as inventory items (See screenshot above as example)
Note: This package was developed and tested with vCO 184.108.40.206 and vCAC 6.1. Please notify me of any issues under vRO 6.0 and vRA 6.2 using the comments here.