https://www.why-did-it.fail/tags/api/Recent content in API on Why did IT failHugo -- gohugo.ioenCopyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.Mon, 18 Sep 2023 00:00:00 +0000https://www.why-did-it.fail/blog/2023-02-nsxt-api-lrp-quicknote/Mon, 18 Sep 2023 00:00:00 +0000https://www.why-did-it.fail/blog/2023-02-nsxt-api-lrp-quicknote/A collegue approached me with a customer request that concerned the NSX-T APIs. More specifically the customer is already using the NSX-T API in management mode but didn’t find the equivalent in the policy API. Doing my own research, I also failed to find the API right away. This post is basicially a reminder to check on the “realized” state and get the head around the desired state of the NSX-T policy API.https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/Wed, 12 Oct 2022 00:00:00 +0000https://www.why-did-it.fail/blog/2022-05-how-to-query-hcl-api/Yet again, customer questions make the best blog posts. This time, it’s about retrieving the firmware and drivers from an ESXi host. So far, the customer uses esxcli which required either PowerCLI or direct SSH access, both were not the preferred choices in this case. High-level overview Starting with vSphere 7, vSphere Lifecycle Manager (vLCM) can handle this task. This blog post will show you how to create a HCL report for a given host which contains all the required information about firmware and drivers, as well as the bonus information about the support status of the system and devices.https://www.why-did-it.fail/blog/2022-04-howto-attatch-clib-iso/Thu, 14 Jul 2022 00:00:00 +0000https://www.why-did-it.fail/blog/2022-04-howto-attatch-clib-iso/A few days ago I was asked by a customer on how to attach an ISO file to a VM using RestAPI calls in the vCenter. Having never done this before I had a look at the problem today and want to share the steps with you. High-level overview Assuming you uploaded the ISO file to the content library prior to reading this, you need to obtain three information before you can attach an ISO file:https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/Tue, 16 Mar 2021 00:00:00 +0000https://www.why-did-it.fail/blog/2021-03-tag-vcenter-object/I am working on enhancing my vSphere release tagging script with the ability to tag the vCenter with a human-readable release name. As shown in the screenshot, it’s easy enough in the UI. Tags applied to the vCenter in the UI However, in PowerCLI there is no commandlet like get-vcenter. After many tries I gave up trying to force the object returned from $global:DefaultVIServers[0] to accept any tag-related operations. Today, I had the idea of working backwards from the assigned tags with Get-TagAssignmenthttps://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/Fri, 05 Mar 2021 00:00:00 +0000https://www.why-did-it.fail/blog/2021-02-set-esxi-release-names-with-tags/Update [2022-10-17] The VMware APIs for the KnowledgeBase have introduced a breaking change. This means the releases can no longer be updated without further development. Update [2021-03-09] The repository has been renamed to VMware-vSphere-Release-Tagging as the future scope should include the vCenter as well. Thank you for all the feedback! In this blog post I want to show you a practial application for the automation that I have built in my last project: