<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>icinga, branch HEAD</title>
<subtitle>Icinga2 API client in Go
</subtitle>
<entry>
<id>bd9616a8e48b8a2f05021f71883d555b874c97e4</id>
<published>2023-04-27T03:19:53Z</published>
<updated>2023-04-27T03:19:53Z</updated>
<title type="text">[v0.1.0] Always return a usable Client</title>
<link rel="alternate" type="text/html" href="commit/bd9616a8e48b8a2f05021f71883d555b874c97e4.html" />
<author>
<name>Oliver Lowe</name>
<email>o@olowe.co</email>
</author>
<content type="text">commit bd9616a8e48b8a2f05021f71883d555b874c97e4
parent 2f7e40d9e97ce934b511c4468f323f9fbaa27f29
Author: Oliver Lowe &lt;o@olowe.co&gt;
Date:   Thu, 27 Apr 2023 13:19:53 +1000

Always return a usable Client

Just because we have an error connecting to the server doesn&#39;t mean
the client&#39;s configuration is invalid. Callers can inspect the error
we return and decide what to do with the returned client.

</content>
</entry>
</feed>
