Dev tools Doc updates (#331)

docs/content/tools/collector/_index.md

@@ -61,14 +61,14 @@ The filtering capabilities are designed for targeting specific Azure resources,
 - If you set a subscription filter for `subscription1` and you also set a resource group filter for `subscription1/resourcegroups/rg-demo1` your results will contain **all** of the resources in `subscription1`
   - This is because we specified `subscription1` and so all of `subscription1` will be evaluated. If we only wanted to evaluate `subscription1/resourcegroups/rg-demo1` then we would include that resource group as a filter and not the full subscription.
 - If you set a subscription filter for `subscription2` and a resourcegroup filter for `subscription1/resourcegroups/rg-demo1` you will evaluate all of `subscription2` and only the resource group `rg-demo-1`.
-- Setting a subscription filter for `subscription3`, a resource group filter for `subscription1/resourcegroups/rg-demo1`, and a tag filter for `env==prod` will return **only resources or those in resource groups tagged with env==prod within subscription3 and subscription1/resourcegroups/rg-demo1.**
+- Setting a subscription filter for `subscription3`, a resource group filter for `subscription1/resourcegroups/rg-demo1`, and a tag filter for `env=~prod` will return **only resources or those in resource groups tagged with env=~prod within subscription3 and subscription1/resourcegroups/rg-demo1.**
 
 ### Tagging Format
 For the WARA script tags are case insensitive.
 
 Tags provided to the WARA script can be broken into two distinct types:
-- == Equals
-- =/ Not Equals
+- =~ Equals
+- !~ Not Equals
 
 These tags can be further broken down into their Key:Value pairs and allow for the following logical operands:
 - || or
@@ -77,24 +77,24 @@ This allows you to build logical tag filtering:
 - The following example shows where the tag name can be App or Application and the value attributed to these tag names must be App1 or App2. In addition, a new entry acts as an **AND** operator. So the first line must be true, so must the second line where we state that the tag name can be env or environment and the value can be prod or production. Finally, we say the tag name region must equal the tag value useast. Only when all of these criteria are met would a resource become included in the output file.
 ```text
 [tags]
-App||Application==App1||App2
-env||environment==prod||production
-region==useast
+App||Application=~App1||App2
+env||environment=~prod||production
+region=~useast
 ```
 In PowerShell this looks like:
 ```powershell
--tags "App||Application==App1||App2","env||environment==prod||production","region==useast"
+-tags "App||Application=~App1||App2","env||environment=~prod||production","region=~useast"
 ```
 - Our next example will demonstrate how we can filter using a **NOT** operator. This will return all resources in scope, except those that meet the requirements of app or application not equalling App3, env or environment not equalling dev or qa, and the region not equalling uswest.
 ```text
 [tags]
-App||Application=/App3
-env|environment=/dev||qa
-region=/uswest
+App||Application!~App3
+env|environment!~dev||qa
+region!~uswest
 ```
 In PowerShell this looks like:
 ```powershell
--tags "App||Application=/App3","env|environment=/dev||qa","region=/uswest"
+-tags "App||Application!~App3","env|environment!~dev||qa","region!~uswest"
 ```
 # Runbooks
 > __Important__: Runbooks are an advanced feature designed for specific workload-aligned use cases. If you're not sure if you need runbooks, you probably don't. Before diving into runbooks, [try using the filtering feature to see if it meets your needs](#filtering).
@@ -116,12 +116,12 @@ Run against one subscription and one resource group in tenant `00000000-0000-000
 ## Example 3
 Run against two subscriptions and one resource group in tenant using tags to filter resources within the scope of the subscription and resource group in the tenant`00000000-0000-0000-0000-000000000000`:
 ```powershell
-.\1_wara_collector.ps1 -TenantID "00000000-0000-0000-0000-000000000000" -SubscriptionIds "/subscriptions/00000000-0000-0000-0000-000000000000","/subscriptions/33333333-3333-3333-3333-333333333333" -ResourceGroups "/subscriptions/55555555-5555-5555-5555-555555555555/resourceGroups/Demo1-RG" -Tags 'Criticality==High','Env==Prod'
+.\1_wara_collector.ps1 -TenantID "00000000-0000-0000-0000-000000000000" -SubscriptionIds "/subscriptions/00000000-0000-0000-0000-000000000000","/subscriptions/33333333-3333-3333-3333-333333333333" -ResourceGroups "/subscriptions/55555555-5555-5555-5555-555555555555/resourceGroups/Demo1-RG" -Tags 'Criticality=~High','Env=~Prod'
 ```
 ## Example 4
 Run against one subscription and two resource groups in tenant `00000000-0000-0000-0000-000000000000` using tags to filter resources within the scope of the subscription and resource group in the tenant`00000000-0000-0000-0000-000000000000`:
 ```powershell
-.\1_wara_collector.ps1 -TenantID "00000000-0000-0000-0000-000000000000" -SubscriptionIds "/subscriptions/00000000-0000-0000-0000-000000000000" -ResourceGroups "/subscriptions/55555555-5555-5555-5555-555555555555/resourceGroups/Demo1-RG","/subscriptions/44444444-4444-4444-4444-444444444444/resourceGroups/Demo2-RG" -Tags 'Criticality==High','Env==Prod'
+.\1_wara_collector.ps1 -TenantID "00000000-0000-0000-0000-000000000000" -SubscriptionIds "/subscriptions/00000000-0000-0000-0000-000000000000" -ResourceGroups "/subscriptions/55555555-5555-5555-5555-555555555555/resourceGroups/Demo1-RG","/subscriptions/44444444-4444-4444-4444-444444444444/resourceGroups/Demo2-RG" -Tags 'Criticality=~High','Env=~Prod'
 ```
 **Note**: Multiple values do not have to be in the same subscription. You can specify multiple resource groups in unique subscriptions.
 ## Example 5
@@ -143,7 +143,7 @@ Run a configuration file:
 
 [tags]
 env==prod
-application==demoapp1
+application=~demoapp1
 ```
 **Note**: In a configuration file we separate multiple entries for a filter by new lines. Where as, from the command line we would pass multiple subscriptions or resource groups using the "string1","string2" pattern. The configuration file is useful for repeated runs, or numerous filters where it may be difficult to troubleshoot syntax in the command line.
 
@@ -204,13 +204,13 @@ Run a runbook
 ### SubscriptionIds
 - **Type**: String Array
 - **Description**: Specifies the subscription IDs to be included in the review. Multiple subscription IDs should be separated by commas. Subscription IDs must be in either GUID form (e.g., `00000000-0000-0000-0000-000000000000`) or full subscription ID form (e.g., `/subscriptions/00000000-0000-0000-0000-000000000000`).
-- *Optional*
+- *Required* (If no -ConfigFile or -ResourceGroup is used)
 - **Note**: Can't be used in combination with `-ConfigFile` parameter.
 
 ### ResourceGroups
 - **Type**: String Array
 - **Description**: Specifies the resource groups to be included in the review. Multiple resource groups should be separated by commas. Resource groups must be in full resource group ID form (e.g., `/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg1`).
-- *Optional*
+- *Required* (If no -ConfigFile or -SubscriptionIds is used)
 - **Note**: Can't be used in combination with `-ConfigFile` or `-RunbookFile` parameters.
 
 ### Tags
@@ -222,7 +222,7 @@ Run a runbook
 ### TenantID
 - **Type**: String
 - **Description**: Specifies the Entra tenant ID to be used to authenticate to Azure.
-- *Required*
+- *Required* (If no -ConfigFile is used)
 
 ### AzureEnvironment
 - **Type**: String