Development: Fix ansible-lint

[bensofficial]

Summary by CodeRabbit

• Style
  • Standardized YAML document start markers across multiple host configuration files to ensure consistent formatting and parsing behavior.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Added YAML document start markers (---) to multiple host_vars files by replacing leading blank lines; no keys or values were changed and no public/exported declarations were modified.

Changes

Cohort / File(s)	Summary
Nodes host_vars/node1.staging2.artemis.cit.tum.de.yml, host_vars/node2.staging2.artemis.cit.tum.de.yml, host_vars/node3.staging2.artemis.cit.tum.de.yml	Inserted YAML document start marker (---) at the top of each file; content/keys unchanged.
Agents host_vars/agent01.staging2.artemis.cit.tum.de.yml, host_vars/agent02.staging2.artemis.cit.tum.de.yml, host_vars/agent03.staging2.artemis.cit.tum.de.yml	Inserted YAML document start marker (---) at the top of each file; content/keys unchanged.
Services & Infrastructure host_vars/proxy.staging2.artemis.cit.tum.de.yml, host_vars/redis.staging2.artemis.cit.tum.de.yml, host_vars/broker.staging2.artemis.cit.tum.de.yml, host_vars/registry.staging2.artemis.cit.tum.de.yml, host_vars/storage.staging2.artemis.cit.tum.de.yml, host_vars/db.staging2.artemis.cit.tum.de.yml	Inserted YAML document start marker (---) at the top of each file; content/keys unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I nibble dashes at the top with glee,

---< the file now greets the YAML sea,
Keys untouched, I leave them all intact,
A tidy header—simple, swift, and exact,
Hop, hop — configuration tidy as can be.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Development: Fix ansible-lint' clearly and concisely summarizes the main change across all files—adding YAML document start markers to resolve ansible-lint issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/ansible-lint

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@host_vars/registry.staging2.artemis.cit.tum.de.yml`:
- Line 1: The PR only adds the YAML document-start marker to
registry.staging2.artemis.cit.tum.de.yml while 60+ other host_vars files are
missing the same '---' header; either update all affected host_vars YAML files
or clearly document the limited scope in the commit message. Fix option A:
batch-add the document-start to all host_vars/*.yml (e.g.,
registry.staging1/prod, agent*, broker*, db*, node*, storage*, proxy* files) by
inserting a leading '---' where missing (use a script or sed/awk to detect files
not starting with '---' and prepend it), commit those changes in this PR. Fix
option B: if you only intend to touch registry.staging2.artemis.cit.tum.de.yml,
update the PR/commit message and description to explicitly state why only that
file is changed and list that follow-up work will address the remaining
host_vars files. Ensure the change references the filename
registry.staging2.artemis.cit.tum.de.yml (and list of other affected patterns)
so reviewers know which files were considered.