<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>json on Why did IT fail</title><link>https://www.why-did-it.fail/tags/json/</link><description>Recent content in json on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Mon, 01 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/json/index.xml" rel="self" type="application/rss+xml"/><item><title>Providing machine readable VMware release data</title><link>https://www.why-did-it.fail/blog/2021-01-vmware-releases-python/</link><pubDate>Mon, 01 Mar 2021 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2021-01-vmware-releases-python/</guid><description>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.
I started a project with the goal to re-format VMware product release information in a way that can be used in automation and scripting. These days, even Excel can handle JSON. When searching for new projects I often need some external trigger to take the first step.</description></item></channel></rss>