From 2fa93705d4d59b2b593850b2ddd502f6d970f299 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=B6rg=20Sachse?= <joerg.sachse@slub-dresden.de>
Date: Thu, 19 Jan 2023 09:26:14 +0100
Subject: [PATCH] style: satisfy Molecule lint

---
 tasks/configure_network.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tasks/configure_network.yml b/tasks/configure_network.yml
index bb1956c..269efcd 100644
--- a/tasks/configure_network.yml
+++ b/tasks/configure_network.yml
@@ -1,7 +1,7 @@
 ---
 # Sooo, WTF is this?
 # In Debian 11 Bullseye's default configuration, network is managed by
-#`ifupdown`. This is OK until you try to use NFS mounts, because they require
+# `ifupdown`. This is OK until you try to use NFS mounts, because they require
 # the network to be fully up and reachable. As `ifupdown` won't properly report
 # the actual network status, SystemD will try to mount NFS shares too early and
 # fail inevitably, because the network is not reachable yet.
@@ -61,4 +61,4 @@
 # The network changes require a reboot, so do that.
 - name: reboot system
   ansible.builtin.reboot:
-  changed_when: False
+  changed_when: false
-- 
GitLab