docs: add wildcard pattern matching to filter docs and templates

Update filter documentation, getting-started guide, extract command
reference, and the filter config template to document wildcard
pattern support (* and ? characters). Fix getting-started.md using
the old apiNames key instead of apis.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Peter Hauge

docs/commands/extract.md

@@ -95,17 +95,19 @@ For local development, `az login` is the simplest option. For CI/CD pipelines, u
 
 By default, `apiops extract` exports **all** resources from the APIM instance (34 resource types including APIs, products, backends, named values, tags, policies, and more).
 
-To extract only specific resources, pass a YAML filter file with `--filter`:
+To extract only specific resources, pass a YAML filter file with `--filter`. Filter entries support exact names and wildcard patterns (`*` for any characters, `?` for a single character):
 
 ```yaml
 # configuration.extractor.yaml
 apis:
   - echo-api
   - petstore-api
+  - prod-*              # Wildcard: all APIs starting with prod-
 products:
   - starter
 backends:
   - backend-api
+  - '*-internal'        # Wildcard: all backends ending with -internal
 namedValues:
   - api-key
 tags:

docs/getting-started.md

@@ -58,9 +58,10 @@ You'll see directories for each resource type — `apis/`, `backends/`, `namedVa
 Extract only the APIs you care about. Create a `filter.yaml`:
 
 ```yaml
-apiNames:
+apis:
   - pet-store-api
   - user-api
+  - staging-*           # Wildcard: all APIs starting with staging-
 ```
 
 ```bash

docs/guides/filtering-resources.md

@@ -72,11 +72,47 @@ namedValues:
 - Simple fields must be an array of strings
 - `apis` and `workspaces` also accept nested object entries for sub-resource filtering (see below)
 - Names are matched case-insensitively against APIM resource names
+- Wildcard patterns are supported — `*` matches any characters, `?` matches a single character (see below)
+- Exact names and wildcard patterns can be mixed in the same array
 - An empty file extracts everything (same as no filter)
 - An empty array (`[]`) excludes ALL resources of that type
 
 ---
 
+## Wildcard Pattern Matching
+
+Filter entries support glob-style wildcard patterns for matching multiple resources by naming convention:
+
+| Wildcard | Meaning | Example |
+|----------|---------|---------|
+| `*` | Matches zero or more characters | `prod-*` matches `prod-api`, `prod-users` |
+| `?` | Matches exactly one character | `api-v?` matches `api-v1`, `api-v2` but not `api-v10` |
+
+### Examples
+
+```yaml
+apis:
+  - '*-test'          # All APIs ending with -test
+  - 'prod-*'          # All APIs starting with prod-
+  - '*-internal-*'    # All APIs containing -internal-
+  - 'v2-*-api'        # APIs following v2-{name}-api pattern
+  - 'echo-api'        # Exact names and patterns can be mixed
+
+products:
+  - 'test-*'          # All test products
+  - '*-starter'       # All starter tier products
+
+backends:
+  - 'backend-*-prod'  # All production backends
+
+namedValues:
+  - '*-connection-string'  # All connection string named values
+```
+
+Wildcard matching is case-insensitive, just like exact matching. Special characters in resource names (e.g., dots in `my.api.v1`) are treated literally — `my.api.*` matches `my.api.test` but not `myXapiXtest`.
+
+---
+
 ## Nested Sub-Resource Filtering
 
 ### API sub-resource filters
@@ -268,6 +304,20 @@ backends:
 
 There is no "exclude" syntax. To extract everything except certain resources, list all the resources you _do_ want. For large instances, it's often easier to extract everything and use `.gitignore` or separate branches to manage visibility.
 
+### Pattern-Based Team Filtering
+
+Using wildcard patterns to extract resources by naming convention:
+
+```yaml
+# configuration.extractor.yaml
+apis:
+  - 'team-payments-*'     # All APIs owned by the payments team
+namedValues:
+  - 'payments-*'          # All named values for payments
+backends:
+  - '*-payments-*'        # All backends related to payments
+```
+
 ---
 
 ## Tips
@@ -276,6 +326,7 @@ There is no "exclude" syntax. To extract everything except certain resources, li
 - **One filter per team** — In multi-team setups, each team maintains its own `configuration.extractor.yaml`
 - **Commit the filter file** — Keep it in version control alongside your artifacts so CI/CD pipelines can use it
 - **Case-insensitive matching** — Filter values are matched case-insensitively against APIM resource names
+- **Use wildcard patterns** — `*` and `?` patterns let you match resources by naming convention instead of listing each name individually
 - **Validate early** — The config loader validates filter entries and will throw `Failed to load filter config` on invalid YAML. Unknown top-level keys produce a warning.
 
 ---

src/templates/configs/filter-config.ts

@@ -11,10 +11,12 @@ export function generateFilterConfig(): string {
 # For full format details and examples, see:
 # https://github.com/Azure/apiops-cli/blob/main/docs/guides/filtering-resources.md
 
-# Extract only specific APIs by name
+# Extract only specific APIs by name (or wildcard pattern)
 # apis:
 #   - echo-api
 #   - petstore-api
+#   - prod-*                        # Wildcard: all APIs starting with prod-
+#   - *-internal-*                  # Wildcard: all APIs containing -internal-
 
 # Advanced: Filter API sub-resources (operations, diagnostics, schemas, releases)
 # apis:
@@ -23,6 +25,7 @@ export function generateFilterConfig(): string {
 #       operations:
 #         - get-pets
 #         - create-pet
+#         - list-*                    # Wildcard: all operations starting with list-
 #       diagnostics:
 #         - applicationinsights
 #       schemas: []                   # Exclude all schemas
@@ -116,5 +119,9 @@ export function generateFilterConfig(): string {
 #   Example:
 #   gateways: []
 #   subscriptions: []
+# - Use * to match any characters: prod-* matches prod-api, prod-users
+# - Use ? to match a single character: api-v? matches api-v1, api-v2
+# - Exact names and wildcard patterns can be mixed in the same list
+# - All matching is case-insensitive
 `;
 }