Have you ever heard about Fling “VMware vRealize Build Tools“, sometimes we also use different names such as #COE development tools, #vRO integration with VSCode, IaC for vRealize Suite or any other name that comes into mind.
You may see quick video what is all about below:
If you have ever heard about it and tried to implement!! OMG!!! Really OMG!!! That’s is really a pain!
Couple of use cases works fine for it, maybe you have a team of developers in house or has a fixed environment to work with it! Yes, that may be worth to expend couple of days on the setup and couple of months on training your personal!
@vdgMichael and myself @JoseCavalheri, we are consultants for a company specialized in VMware products and as you can imagine, we are vRealize Automation and Orchestrator guys 🙂
In this type of approach is almost impossible to have a setup like above, hence we came up with a different approach, something that would take less effort and more benefits to us both!
Hence the question came : Why we don’t export our Actions and Configuration Elements to a central repository? In this case our requirements were quite simple and we came up with a list below
- Don’t turn on your own vRO server everytime you need something similar
- Share within ourselves and our internal team all the actions created by us
- Don’t reinvent the wheel! If you have ever created a “Add CPU” or a “Add RAM”, just reuse/re-adapt
- Quality! Quality! Quality! >> Yes!! If you build it once nicely, that will guarantee you that!
- vRA 8x transitions came along too! More and more customers want it! Hence, always changing from VCACCafe and similar actions will be pretty handy to have it out of the shelve!
- Any many others… anyway… you got the point!
So that was the challenge and we accepted! We came up with the following easy solution:
1- Every vRO Package we have, we export the actions and configuration elements;
2- Easy way to add to a GitHub repository
3- All Actions Parameters must be clear with input,types and description when possible(* Auto exported);
4- All Configuration Elements with input,types and description when possible(* Auto exported);
Attention: Here is some good difference between this solution and Fling. We are using for consultation, reuse and improvements, but there is ” NO LINK” to any vRO. We are just talking about *.js code and git repository.
Hereby you can see the result from our solution (script based export).
We have defined the structure we wanted, let’s say a repository for vRA7x and one for vRA8x + Actions, Configuration Elements, CloudTemplates,etc…
OUR CORE MESSAGE is SHARE TO COMMUNITY !
Hence here it is … The code is written in PowerShell and it works in both Windows and MAC.
There is no needed to read the code, basically it ask for:
1 – Where is your vRO Package folder (after unzipped it )
2 – Where do you want to save it
3 – Windows or Mac
4 – Few seconds, just go and check folder location. 🙂
Don’t forget the flexibility of VSCode Search as well! If you want to search specific code, just type the search and it will show all actions available for you with examples/similar code within your repository.
At this moment,we didn’t include the script in a open repository, but it is a good start point!
Hope you enjoy it!
See you next at next blog post! Regards Jose Cavalheri.
One thought on “Export vRO Packages to Actions & Configuration Elements (*.js files) + Create your own Git Repository”
That’s so useful.
LikeLiked by 1 person