<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>openstack/openstack-ansible-haproxy_server — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-openstack-ansible-haproxy_server/</link>
    <atom:link href="https://stackers.network/projects/openstack-openstack-ansible-haproxy_server/feed.xml" rel="self" type="application/rss+xml"/>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate>
    <description>Weekly code-activity digest for openstack/openstack-ansible-haproxy_server from Stackers Network.</description>
    <item>
      <title>openstack/openstack-ansible-haproxy_server — Week of 2026-10-03</title>
      <link>https://stackers.network/projects/openstack-openstack-ansible-haproxy_server/2026-10-03</link>
      <guid>https://stackers.network/projects/openstack-openstack-ansible-haproxy_server/2026-10-03</guid>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
      <description>Testing coverage. The dominant change this week is a ~1,200-line addition of extensive molecule tests for the role, giving the HAProxy role proper scenario-based coverage for the first time (1005786). Frontend and backend fixes. TLS termination is now permitted for TCP…</description>
      <content:encoded><![CDATA[<p><strong>Testing coverage.</strong> The dominant change this week is a ~1,200-line addition of extensive molecule tests for the role, giving the HAProxy role proper scenario-based coverage for the first time (<a href="https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/1005786">1005786</a>).</p>
<p><strong>Frontend and backend fixes.</strong> TLS termination is now permitted for TCP frontends, unblocking configurations that pair TLS offload with non-HTTP backends. The removal of the <code translate="no">httpchk</code> option was reverted after it turned out to still be needed, with the revert carried across master and stable branches.</p>
<p><strong>Packaging and distribution.</strong> GPG key distribution was reordered to ensure the key is in place before import is attempted, and a set of fixes addresses ansible-galaxy fetching issues, also backported across branches.</p>
<p>Elsewhere, the week is otherwise quiet — several of the eleven merges are the same fix landing on multiple stable branches rather than new work.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
