Featured Member: Brian Bunke

There are so many great people connecting through the VMware {code} program, it’s hard to keep track. This week, we’re introducing a new feature here on the VMware {code} blog: brief interviews with some of our key contributors to help everyone get a better sense of what’s going on.

Below is the first one. As always, we love to hear your feedback in the comments below, on Twitter or on Slack. If you’d like to be interviewed or know someone we should feature – please get in touch. Thanks!

Who are you, what do you do, and what brings you to VMware {code}?

My name is Brian Bunke, and I’m a Systems Automator for a manufacturing customer in the Seattle area. I joined the VMware {code} community because I interact with VMware products often, and I’m passionate about developing and improving tooling that fellow admins and I consume in our day-to-day lives. Currently, most of my work in the {code} community has revolved around the Vester project.

Briefly, what is Vester?

Vester is a community-driven, open source project written in PowerShell. It uses PowerCLI and Pester to provide a lightweight configuration management solution for VMware administrators. Vester runs tests to ensure your environment matches your config file, and is capable of automatically fixing any problems it finds.

Neat! How can people get involved?

A main goal of maintaining Vester is making tests easy to write and contribute. We hope this interests users in giving a little something back to the project! If you’re interested in learning more, you can review my three-part blog series on how to get started.

You recently shared some code via VMware {code} Sample Exchange. What was that about? And what was your experience?

I wrote a PowerShell function, Get-VMotion, because I found I was reviewing vMotion history often enough that it was worth packaging into a simple command. I wanted to provide it to the community as a way to pay it forward, and the Sample Exchange has some really slick integration with GitHub that made sharing very simple.

Any other ways you’ve made use of this piece of functionality on the VMware {code} website?

The “Requests” area is a cool idea that hasn’t seen much traction yet. If you have an idea for some code that you’re not sure how to write, you can post your request to the community at large. Maybe someone else agrees that it’s a problem worth solving, and has the means to do so!

VMware {code} was launched about a year or so ago. What would you like to see going forward? As we continue to grow and evolve the program, where do you see the biggest opportunities?

I believe there is still a lot of untapped potential in unlocking the developer community on common goals. The Slack team is a great way to self-organize, and I hope {code} can continue to promote those contributions. If community work is encouraged and celebrated, more will be incentivized to participate, and the VMware ecosystem will continue to flourish.

Thanks, Brian! Where can people find you online?

Thanks for the opportunity! I blog at, and you can find me as @brianbunke on Twitter, GitHub, and Slack.


Leave a Reply

Your email address will not be published. Required fields are marked *