From 3e59fe709c13c9ed5a03c6a026eebf4a6d805ddc Mon Sep 17 00:00:00 2001
From: Michele Cereda <cereda.michele@gmail.com>
Date: Tue, 5 Aug 2025 17:05:17 +0200
Subject: [PATCH] chore: dump sources

---
 knowledge base/ansible.md                 |  6 ++
 knowledge base/cloud computing/aws/ec2.md |  2 +
 knowledge base/cloud computing/aws/ssm.md |  2 +
 knowledge base/haproxy.md                 | 68 +++++++++++++++++++++++
 knowledge base/needs-restarting.md        |  7 ++-
 5 files changed, 82 insertions(+), 3 deletions(-)
 create mode 100644 knowledge base/haproxy.md

diff --git a/knowledge base/ansible.md b/knowledge base/ansible.md
index eb119d4..f05b2e3 100644
--- a/knowledge base/ansible.md	
+++ b/knowledge base/ansible.md	
@@ -28,6 +28,7 @@
 1. [Ansible Navigator](#ansible-navigator)
     1. [Navigator configuration files](#navigator-configuration-files)
 1. [Secrets management](#secrets-management)
+    1. [Hiding sensitive values in verbose runs](#hiding-sensitive-values-in-verbose-runs)
     1. [Ansible Vault](#ansible-vault)
 1. [Best practices](#best-practices)
 1. [Troubleshooting](#troubleshooting)
@@ -1047,6 +1048,10 @@ Use **interactive prompts** to ask for values at runtime.
 
 Use [Ansible Vault] for automated execution when one does **not** require using specific secrets or password managers.
 
+### Hiding sensitive values in verbose runs
+
+Refer [Hide sensitive data in Ansible verbose logs].
+
 ### Ansible Vault
 
 Refer [Protecting sensitive data with Ansible Vault], [Ansible Vault tutorial] and [Ansible Vault with AWX].
@@ -1768,3 +1773,4 @@ Another _better (?)_ solution in playbooks/roles would be to sanitize the input
 [working with versions]: https://docs.ansible.com/ansible/latest/collections/community/general/docsite/filter_guide_working_with_versions.html
 [yes and no, true and false]: https://chronicler.tech/red-hat-ansible-yes-no-and/
 [zuul]: https://zuul-ci.org/
+[Hide sensitive data in Ansible verbose logs]: https://harshanu.space/en/tech/ansible-redact/
diff --git a/knowledge base/cloud computing/aws/ec2.md b/knowledge base/cloud computing/aws/ec2.md
index 0cd7350..6d89692 100644
--- a/knowledge base/cloud computing/aws/ec2.md	
+++ b/knowledge base/cloud computing/aws/ec2.md	
@@ -238,6 +238,7 @@ Also see [Automatic instance recovery].
 - [Monitor AWS EC2 memory utilization and set CloudWatch Alarm]
 - [Automating Instance Reboots with Amazon CloudWatch EC2 Actions]
 - [Understanding AWS Tenancy Options]
+- [Find AMIs with the SSM Agent preinstalled]
 
 <!--
   Reference
@@ -279,6 +280,7 @@ Also see [Automatic instance recovery].
 [unlimited mode for burstable performance instances]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-unlimited-mode.html
 [using al2023 based amazon ecs amis to host containerized workloads]: https://docs.aws.amazon.com/linux/al2023/ug/ecs.html
 [using instance profiles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html
+[Find AMIs with the SSM Agent preinstalled]: https://docs.aws.amazon.com/systems-manager/latest/userguide/ami-preinstalled-agent.html
 
 <!-- Others -->
 [Automating Instance Reboots with Amazon CloudWatch EC2 Actions]: https://devops.supportsages.com/automating-instance-reboots-with-amazon-cloudwatch-ec2-actions-375f633a658d
diff --git a/knowledge base/cloud computing/aws/ssm.md b/knowledge base/cloud computing/aws/ssm.md
index fe532d7..9c9a086 100644
--- a/knowledge base/cloud computing/aws/ssm.md	
+++ b/knowledge base/cloud computing/aws/ssm.md	
@@ -396,6 +396,7 @@ $ sudo ssm-cli get-diagnostics --output 'table'
 - [Using Ansible in AWS]
 - [Troubleshooting managed node availability]
 - [Troubleshooting managed node availability using `ssm-cli`][troubleshooting managed node availability using ssm-cli]
+- [Find AMIs with the SSM Agent preinstalled]
 
 <!--
   Reference
@@ -422,6 +423,7 @@ $ sudo ssm-cli get-diagnostics --output 'table'
 [start a session]: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-sessions-start.html
 [troubleshooting managed node availability using ssm-cli]: https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-cli.html
 [troubleshooting managed node availability]: https://docs.aws.amazon.com/systems-manager/latest/userguide/troubleshooting-managed-instances.html
+[Find AMIs with the SSM Agent preinstalled]: https://docs.aws.amazon.com/systems-manager/latest/userguide/ami-preinstalled-agent.html
 
 <!-- Others -->
 [ansible temp dir change]: https://devops.stackexchange.com/questions/10703/ansible-temp-dir-change
diff --git a/knowledge base/haproxy.md b/knowledge base/haproxy.md
new file mode 100644
index 0000000..b1cdcad
--- /dev/null
+++ b/knowledge base/haproxy.md	
@@ -0,0 +1,68 @@
+# HAProxy
+
+> TODO
+
+Intro
+
+<!-- Remove this line to uncomment if used
+## Table of contents <!-- omit in toc -->
+
+1. [TL;DR](#tldr)
+1. [Further readings](#further-readings)
+   1. [Sources](#sources)
+
+## TL;DR
+
+<!-- Uncomment if used
+<details>
+  <summary>Setup</summary>
+
+```sh
+```
+
+</details>
+-->
+
+<!-- Uncomment if used
+<details>
+  <summary>Usage</summary>
+
+```sh
+```
+
+</details>
+-->
+
+<!-- Uncomment if used
+<details>
+  <summary>Real world use cases</summary>
+
+```sh
+```
+
+</details>
+-->
+
+## Further readings
+
+- [Website]
+- [Codebase]
+
+### Sources
+
+- [Documentation]
+
+<!--
+  Reference
+  ═╬═Time══
+  -->
+
+<!-- In-article sections -->
+<!-- Knowledge base -->
+<!-- Files -->
+<!-- Upstream -->
+[codebase]: https://github.com/haproxytech
+[documentation]: https://www.haproxy.com/documentation/
+[website]: https://www.haproxy.com/
+
+<!-- Others -->
diff --git a/knowledge base/needs-restarting.md b/knowledge base/needs-restarting.md
index 18ba4f6..469bccd 100644
--- a/knowledge base/needs-restarting.md	
+++ b/knowledge base/needs-restarting.md	
@@ -2,8 +2,6 @@
 
 `needs-restarting -r` returns 1 if a reboot is needed, and 0 if it is not.
 
-## Table of contents <!-- omit in toc -->
-
 1. [TL;DR](#tldr)
 1. [Sources](#sources)
 
@@ -42,10 +40,13 @@ Reboot is required to ensure that your system benefits from these updates.
 ## Sources
 
 - [Automatic Reboot on Kernel Update]
+- [How to check if CentOS / RHEL needs a full reboot]
 
 <!--
-  References
+  Reference
+  ═╬═Time══
   -->
 
 <!-- Others -->
 [automatic reboot on kernel update]: https://access.redhat.com/discussions/3106621#comment-1196821
+[How to check if CentOS / RHEL needs a full reboot]: https://www.cyberciti.biz/faq/how-to-check-if-centos-rhel-needs-a-full-reboot/