chore: dump sources

This commit is contained in:
Michele Cereda
2025-08-05 17:05:17 +02:00
parent 475e72983e
commit 3e59fe709c
5 changed files with 82 additions and 3 deletions

View File

@@ -28,6 +28,7 @@
1. [Ansible Navigator](#ansible-navigator) 1. [Ansible Navigator](#ansible-navigator)
1. [Navigator configuration files](#navigator-configuration-files) 1. [Navigator configuration files](#navigator-configuration-files)
1. [Secrets management](#secrets-management) 1. [Secrets management](#secrets-management)
1. [Hiding sensitive values in verbose runs](#hiding-sensitive-values-in-verbose-runs)
1. [Ansible Vault](#ansible-vault) 1. [Ansible Vault](#ansible-vault)
1. [Best practices](#best-practices) 1. [Best practices](#best-practices)
1. [Troubleshooting](#troubleshooting) 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. 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 ### Ansible Vault
Refer [Protecting sensitive data with Ansible Vault], [Ansible Vault tutorial] and [Ansible Vault with AWX]. 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 [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/ [yes and no, true and false]: https://chronicler.tech/red-hat-ansible-yes-no-and/
[zuul]: https://zuul-ci.org/ [zuul]: https://zuul-ci.org/
[Hide sensitive data in Ansible verbose logs]: https://harshanu.space/en/tech/ansible-redact/

View File

@@ -238,6 +238,7 @@ Also see [Automatic instance recovery].
- [Monitor AWS EC2 memory utilization and set CloudWatch Alarm] - [Monitor AWS EC2 memory utilization and set CloudWatch Alarm]
- [Automating Instance Reboots with Amazon CloudWatch EC2 Actions] - [Automating Instance Reboots with Amazon CloudWatch EC2 Actions]
- [Understanding AWS Tenancy Options] - [Understanding AWS Tenancy Options]
- [Find AMIs with the SSM Agent preinstalled]
<!-- <!--
Reference 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 [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 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 [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 --> <!-- Others -->
[Automating Instance Reboots with Amazon CloudWatch EC2 Actions]: https://devops.supportsages.com/automating-instance-reboots-with-amazon-cloudwatch-ec2-actions-375f633a658d [Automating Instance Reboots with Amazon CloudWatch EC2 Actions]: https://devops.supportsages.com/automating-instance-reboots-with-amazon-cloudwatch-ec2-actions-375f633a658d

View File

@@ -396,6 +396,7 @@ $ sudo ssm-cli get-diagnostics --output 'table'
- [Using Ansible in AWS] - [Using Ansible in AWS]
- [Troubleshooting managed node availability] - [Troubleshooting managed node availability]
- [Troubleshooting managed node availability using `ssm-cli`][troubleshooting managed node availability using ssm-cli] - [Troubleshooting managed node availability using `ssm-cli`][troubleshooting managed node availability using ssm-cli]
- [Find AMIs with the SSM Agent preinstalled]
<!-- <!--
Reference 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 [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 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 [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 --> <!-- Others -->
[ansible temp dir change]: https://devops.stackexchange.com/questions/10703/ansible-temp-dir-change [ansible temp dir change]: https://devops.stackexchange.com/questions/10703/ansible-temp-dir-change

68
knowledge base/haproxy.md Normal file
View File

@@ -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 -->

View File

@@ -2,8 +2,6 @@
`needs-restarting -r` returns 1 if a reboot is needed, and 0 if it is not. `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. [TL;DR](#tldr)
1. [Sources](#sources) 1. [Sources](#sources)
@@ -42,10 +40,13 @@ Reboot is required to ensure that your system benefits from these updates.
## Sources ## Sources
- [Automatic Reboot on Kernel Update] - [Automatic Reboot on Kernel Update]
- [How to check if CentOS / RHEL needs a full reboot]
<!-- <!--
References Reference
═╬═Time══
--> -->
<!-- Others --> <!-- Others -->
[automatic reboot on kernel update]: https://access.redhat.com/discussions/3106621#comment-1196821 [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/