I thought for a bit of a laugh I would challenge myself to create an ABX action to raise a Jira ticket when a deployment fails. In the end it wasn’t too difficult and it certainly shows that there could be some good further use cases for integration...
If you have reviewed some of my other posts here on automationpro.co.uk, you will know that I’m a fan of the ABX functionality in vRA8. Something that I have been wanting to accomplish for a while is sending an email from an ABX. There are some awesome posts...
Recently I needed to create a connection to a Windows server and perform some operations on it. From there I wanted to run commands on the Windows server itself, and I didn’t want to have to worry about double hop WinRM issues from PowerShell. I wanted something flexible...
Whilst working with a customer to provide extensibility through ABX actions, I came across a documented issue that I wasn’t previously aware of. Whilst testing an ABX action I received the following error message: abx-service [host=’abx-service-app-5c578445f7-j2w6m’ thread=’parallel-47′ user=” org=” trace=” component=’GatewayActionProvider’ method=’convertExceptions:437′ actionRunI d=’8a7480a179b68ffb0179e552568b1e1a’ context=’87aad62e-0d90-4a61-b265-8b3720239a00′ tokenId=’8eb4435a-be1f-4921-9ca3-d809625dce4c’ parentTokenId=’8bdaa86c-1a01-4714-8c8f-9b1d41a5d98f’] c.v.a.a.p.i.g.Gate...
I have been playing around with vra8 actions for a while now and whilst it is a handy function, I have found some issues with the PowerShell implementation. However, Python based actions seem to execute just fine. Whilst playing around I came across what looked like a really...
Recently I have been having some fun and games with vRA 8.2, in particular, with the extensibility capabilities. With the introduction of PowerShell support for vRA actions, I thought I would have a little play and see what I could break. I’m On A MetaData Hunt.. Ok, so...