As then you don't really need to do much in the way of development, as you are just telling the plugin to install your "package".
I think what I need is a step by step guide to
- Tools required (Eclipse/Maven etc) download urls and versions
- Get a basic "hello world" plugin building
- Add my workflows/actions/configurations/resource files (currently in a package) to the plugin (so they are installed on plugin installation)
Then after I get to this stage possibly adding some ui to assist with the configuration of the multiple rest endpoints I am using.
Any further help appreciated as always :-)
Sure! (sorry about the delay in the reply, was busy and got sidetracked)
I was in your position a year ago and so discovered a few webpages that helped my plugin development.
One in particular covers all the points you'd like actually: https://www.helloitscraig.co.uk/2016/04/getting-started-vro-plugin-development-part-1.html
He does a nice walkthrough of how how to setup a skeleton of a plugin that you develop from, and that skeleton is a "Hello World" example.
Although it is for an older vRO and there were some steps that did not work for me. So below are some points that might be useful to know and the steps that I figured out that might help you if you also encounter the same problems I did:
* I found that the 'mvn archetype:generate ...' step does not work with maven 3.x. This might not be the case anymore -> let me know!
** If it doesn't work substitute that for 'mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate' -> which tells it to create the plugin in the maven 2.4 way (which does work)
* Of the archtypes that are presented see (Maven Archetypes), I personally used "annotation": com.vmware.o11n:o11n-archetype-inventory-annotation - As it means I didn't have to faff around with the vso.xml (this file lets vRO know what objects to care about in your plugin)
* He used "Spring tool suite" based on Eclipse, but you can just google Eclipse and download that if you especially want to use that IDE, or use any other Java IDE you want.
additional information that might be worth looking at:
* Structure of an Orchestrator Plug-In - as vRO creates the skeleton of the plugin, but doesn't actually tell you what any of it is!
* Developing Plug-Ins as a lot of info explaining what all the different parts of a plugin should have and do to work with vRO
** although, I didn't really read this before starting, but as I went along!
** but you should probably go through it if you want your plugin to get certified by VMware
* https://vdc-download.vmware.com/vmwb-repository/dcr-public/0fae6f15-fed1-4017-9e6a-fa152e932c7d/cacdad8e-14b3-4234-acdc-… is a VMware's guide to making a vRO plugin from scratch (this also helped, a bit more technical, which is good)
anyway, hope that didn't overwhelm you!
Thanks so much for the advice, will take a look at all of that!