Added Tags to All Docs

operations/automation/ansible/awx/awx-kerberos-implementation.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Kerberos
+  - Automation
+---
+
 ## Kerberos Implementation
 You may find that you need to be able to run playbooks on domain-joined Windows devices using Kerberos.  You need to go through some extra steps to set this up after you have successfully fully deployed AWX Operator into Kubernetes.
 

operations/automation/ansible/awx/connect-awx-to-gitea.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Gitea
+  - Automation
+---
+
 **Purpose**: Once AWX is deployed, you will want to connect Gitea at https://git.bunny-lab.io.  The reason for this is so we can pull in our playbooks, inventories, and templates automatically into AWX, making it more stateless overall and more resilient to potential failures of either AWX or the underlying Kubernetes Cluster hosting it.
 
 ## Obtain Gitea Token

operations/automation/ansible/awx/deployment/awx-in-minikube.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 # Deploy AWX on Minikube Cluster
 Minikube Cluster based deployment of Ansible AWX. (Ansible Tower)
 !!! note Prerequisites

operations/automation/ansible/awx/deployment/awx-operator.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 **Purpose**:
 Deploying a Rancher RKE2 Cluster-based Ansible AWX Operator server.  This can scale to a larger more enterprise environment if needed.
 

operations/automation/ansible/awx/deployment/upgrading-issues-past-2-10-0.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - AWX
+  - Automation
+---
+
 ## Upgrading from 2.10.0 to 2.19.1+
 There is a known issue with upgrading / install AWX Operator beyond version 2.10.0, because of how the PostgreSQL database upgrades from 13.0 to 15.0, and has changed permissions.  The following workflow will help get past that and adjust the permissions in such a way that allows the upgrade to proceed successfully.  If this is a clean installation, you can also perform this step if the fresh install of 2.19.1 is not working yet. (It wont work out of the box because of this bug).  `The developers of AWX seem to just not care about this issue, and have not implemented an official fix themselves at this time).
 

operations/automation/ansible/credentials/custom-credential-types/winrm.md

@@ -1,3 +1,10 @@
+---
+tags:
+  - Ansible
+  - WinRM
+  - Automation
+---
+
 # WinRM (Kerberos)
 **Name**: "Kerberos WinRM"
 

operations/automation/ansible/credentials/overview.md

@@ -1,6 +1,10 @@
 ---
 sidebar_position: 1
+tags:
+  - Ansible
+  - Automation
 ---
+
 # AWX Credential Types
 When interacting with devices via Ansible Playbooks, you need to provide the playbook with credentials to connect to the device with.  Examples are domain credentials for Windows devices, and local sudo user credentials for Linux.
 

operations/automation/ansible/enable-winrm-on-windows-devices.md

@@ -1,3 +1,11 @@
+---
+tags:
+  - Ansible
+  - WinRM
+  - Windows
+  - Automation
+---
+
 **Purpose**: 
 You will need to enable secure WinRM management of the Windows devices you are running playbooks against, as compared to the Linux devices.  The following powershell script needs to be ran on every Windows device you intend to run Ansible playbooks on.  This script can also be useful for simply enabling / resetting WinRM configurations for Hyper-V hosts in general, just omit the Powershell script remote signing section if you dont plan on using it for Ansible.
 

operations/automation/ansible/inventories/overview.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Ansible
+  - Automation
+---
+
 # Host Inventories
 When you are deploying playbooks, you target hosts that exist in "Inventories".  These inventories consist of a list of hosts and their corresponding IP addresses, as well as any host-specific variables that may be necessary to declare to run the playbook.  You can see an example inventory file below.  
 

operations/automation/ansible/playbooks/playbooks.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Ansible
+  - Automation
+---
+
 !!! warning "DOCUMENT UNDER CONSTRUCTION"
     This document is a "scaffold" document.  It is missing significant portions of several sections and should not be read with any scrutiny until it is more feature-complete down-the-road.  Come back later and I should have added more to this document hopefully by then.
 

operations/automation/ansible/projects/overview.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Ansible
+  - Automation
+---
+
 # AWX Projects
 When you want to run playbooks on host devices in your inventory files, you need to host the playbooks in a "Project".  Projects can be as simple as a connection to Gitea/Github to store playbooks in a repository.
 

operations/automation/ansible/templates/overview.md

@@ -1,3 +1,9 @@
+---
+tags:
+  - Ansible
+  - Automation
+---
+
 # Templates
 Templates are basically pre-constructed groups of devices, playbooks, and credentials that perform a specific kind of task against a predefined group of hosts or device inventory.