Normalize DNS and connectivity plugin namespaces

Author: marcofortina

docs/guides/ssh-smoke.md

@@ -49,8 +49,8 @@ remote user. It covers:
 - `fs.object.find`, `fs.permission.mode`
 - `archive.tar`, `archive.untar`, `archive.zip`, `archive.unzip`
 - `transfer.upload`, `transfer.download`, `transfer.sync`
-- `wait.process`
-- `assert.disk`, `assert.tcp`
+- `process.wait`
+- `assert.disk`, `network.connectivity.port_check`
 - artifact capture for stdout/stderr/data
 - resume helpers through the normal run state store
 

docs/plugins/generated.md

@@ -613,40 +613,6 @@ with:
   path: /tmp/automax-demo
 ```
 
-### `assert.tcp`
-
-Assert that a TCP host/port is reachable from the controller.
-
-- Remote session: `false`
-- Dry-run support: `true`
-- Check mode support: `false`
-
-| Parameter | Required | Type | Default | Description |
-|---|---:|---|---|---|
-| `host` | yes | `string` |  | Hostname or IP address to check from the controller. |
-| `port` | yes | `integer` |  | TCP port number. |
-| `connect_timeout` | no | `number` | `3` | Per-attempt TCP connect timeout in seconds. |
-
-Result fields:
-
-- `changed`: Whether the plugin changed the target or controller state.
-- `message`: Human-readable result message.
-- `rc`: Process or command return code when applicable.
-- `stdout`: Captured standard output when applicable.
-- `stderr`: Captured standard error when applicable.
-- `data`: Plugin-specific structured result data.
-- `data.host`: Checked host.
-- `data.port`: Checked TCP port.
-
-Example:
-
-```yaml
-use: assert.tcp
-with:
-  host: 127.0.0.1
-  port: 22
-```
-
 ## auditd
 
 ### `auditd.backlog_assert`
@@ -5862,6 +5828,8 @@ Result fields:
 - `stdout`: Captured standard output when applicable.
 - `stderr`: Captured standard error when applicable.
 - `data`: Plugin-specific structured result data.
+- `data.host`: Checked host.
+- `data.port`: Checked TCP port.
 
 Example:
 
@@ -5872,25 +5840,57 @@ with:
   port: 22
 ```
 
-### `network.dns`
+### `network.connectivity.port_wait`
 
-Configure DNS resolver settings using the backend-aware resolver implementation.
+Wait for TCP or UDP connectivity from the remote target.
 
 - Remote session: `true`
 - Dry-run support: `true`
-- Check mode support: `false`
+- Check mode support: `true`
+
+| Parameter | Required | Type | Default | Description |
+|---|---:|---|---|---|
+| `host` | yes | `string` |  | Hostname or IP address to check from the controller. |
+| `port` | yes | `integer` |  | TCP port number. |
+| `protocol` | no | `string` | `tcp` | Network protocol such as tcp or udp. |
+| `timeout` | no | `number` |  | Operation timeout in seconds. |
+| `interval` | no | `number` | `2` | Polling interval in seconds. |
+| `retries` | no | `integer` | `12` | Maximum polling attempts before a wait operation fails. |
+| `sudo` | no | `boolean` | `False` | Run the remote operation through sudo -n when supported. |
+
+Result fields:
+
+- `changed`: Whether the plugin changed the target or controller state.
+- `message`: Human-readable result message.
+- `rc`: Process or command return code when applicable.
+- `stdout`: Captured standard output when applicable.
+- `stderr`: Captured standard error when applicable.
+- `data`: Plugin-specific structured result data.
+- `data.host`: Checked host.
+- `data.port`: Checked TCP port.
+
+Example:
+
+```yaml
+use: network.connectivity.port_wait
+with:
+  host: 127.0.0.1
+  port: 22
+```
+
+### `network.dns.check`
+
+Assert resolver nameserver, search and option entries from /etc/resolv.conf.
+
+- Remote session: `true`
+- Dry-run support: `true`
+- Check mode support: `true`
 
 | Parameter | Required | Type | Default | Description |
 |---|---:|---|---|---|
-| `backend` | no | `string` |  | Operation backend such as auto, runtime, networkmanager, systemd-networkd, ifcfg, plain-file, systemd-resolved or resolvconf. |
 | `nameservers` | no | `list` |  | Resolver nameserver addresses. |
 | `search` | no | `list` |  | Resolver search domains. |
 | `options` | no | `list` |  | Resolver options. |
-| `path` | no | `path` |  | Remote or local path, depending on the plugin. |
-| `nm_connection` | no | `string` |  | NetworkManager connection profile used for persistent DNS changes. |
-| `force` | no | `boolean` | `False` | Force the operation when supported. |
-| `backup` | no | `boolean` | `False` | Create a backup before modifying an existing file. |
-| `backup_suffix` | no | `string` | `.bak` | Suffix appended to the original path when backup is enabled. |
 | `sudo` | no | `boolean` | `False` | Run the remote operation through sudo -n when supported. |
 
 Result fields:
@@ -5905,26 +5905,33 @@ Result fields:
 Example:
 
 ```yaml
-use: network.dns
+use: network.dns.check
 with:
-  backend: auto
   nameservers:
     - 192.0.2.53
+  search:
+    - example.com
 ```
 
-### `network.dns_assert`
+### `network.dns.config`
 
-Assert resolver nameserver, search and option entries from /etc/resolv.conf.
+Configure DNS resolver settings using the backend-aware resolver implementation.
 
 - Remote session: `true`
 - Dry-run support: `true`
-- Check mode support: `true`
+- Check mode support: `false`
 
 | Parameter | Required | Type | Default | Description |
 |---|---:|---|---|---|
+| `backend` | no | `string` |  | Operation backend such as auto, runtime, networkmanager, systemd-networkd, ifcfg, plain-file, systemd-resolved or resolvconf. |
 | `nameservers` | no | `list` |  | Resolver nameserver addresses. |
 | `search` | no | `list` |  | Resolver search domains. |
 | `options` | no | `list` |  | Resolver options. |
+| `path` | no | `path` |  | Remote or local path, depending on the plugin. |
+| `nm_connection` | no | `string` |  | NetworkManager connection profile used for persistent DNS changes. |
+| `force` | no | `boolean` | `False` | Force the operation when supported. |
+| `backup` | no | `boolean` | `False` | Create a backup before modifying an existing file. |
+| `backup_suffix` | no | `string` | `.bak` | Suffix appended to the original path when backup is enabled. |
 | `sudo` | no | `boolean` | `False` | Run the remote operation through sudo -n when supported. |
 
 Result fields:
@@ -5939,15 +5946,14 @@ Result fields:
 Example:
 
 ```yaml
-use: network.dns_assert
+use: network.dns.config
 with:
+  backend: auto
   nameservers:
     - 192.0.2.53
-  search:
-    - example.com
 ```
 
-### `network.dns_facts`
+### `network.dns.facts`
 
 Detect the active DNS resolver backend without changing resolver configuration.
 
@@ -5971,7 +5977,7 @@ Result fields:
 Example:
 
 ```yaml
-use: network.dns_facts
+use: network.dns.facts
 with:
   sudo: true
 ```
@@ -11607,74 +11613,3 @@ use: user.unlock
 with:
   name: nginx
 ```
-
-## wait
-
-### `wait.process`
-
-Wait until a remote process condition is true.
-
-- Remote session: `true`
-- Dry-run support: `true`
-- Check mode support: `false`
-
-| Parameter | Required | Type | Default | Description |
-|---|---:|---|---|---|
-| `pattern` | yes | `string` |  | Regex, process pattern or search pattern. |
-| `state` | no | `string` |  | Desired state such as present, absent, started or stopped. |
-| `timeout` | no | `number` |  | Operation timeout in seconds. |
-| `interval` | no | `number` | `2` | Polling interval in seconds. |
-| `sudo` | no | `boolean` | `False` | Run the remote operation through sudo -n when supported. |
-
-Result fields:
-
-- `changed`: Whether the plugin changed the target or controller state.
-- `message`: Human-readable result message.
-- `rc`: Process or command return code when applicable.
-- `stdout`: Captured standard output when applicable.
-- `stderr`: Captured standard error when applicable.
-- `data`: Plugin-specific structured result data.
-
-Example:
-
-```yaml
-use: wait.process
-with:
-  pattern: KEY=.*
-```
-
-### `wait.tcp`
-
-Wait until a TCP host/port is reachable from the controller.
-
-- Remote session: `false`
-- Dry-run support: `true`
-- Check mode support: `false`
-
-| Parameter | Required | Type | Default | Description |
-|---|---:|---|---|---|
-| `host` | yes | `string` |  | Hostname or IP address to check from the controller. |
-| `port` | yes | `integer` |  | TCP port number. |
-| `timeout` | no | `number` |  | Operation timeout in seconds. |
-| `interval` | no | `number` | `2` | Polling interval in seconds. |
-| `connect_timeout` | no | `number` | `3` | Per-attempt TCP connect timeout in seconds. |
-
-Result fields:
-
-- `changed`: Whether the plugin changed the target or controller state.
-- `message`: Human-readable result message.
-- `rc`: Process or command return code when applicable.
-- `stdout`: Captured standard output when applicable.
-- `stderr`: Captured standard error when applicable.
-- `data`: Plugin-specific structured result data.
-- `data.host`: Checked host.
-- `data.port`: Checked TCP port.
-
-Example:
-
-```yaml
-use: wait.tcp
-with:
-  host: 127.0.0.1
-  port: 22
-```

docs/plugins/index.md

@@ -35,7 +35,6 @@ archive.untar
 archive.unzip
 archive.zip
 assert.disk
-assert.tcp
 auditd.backlog_assert
 auditd.reload
 auditd.rule
@@ -188,9 +187,10 @@ multipath.flush
 multipath.reload
 multipath.status
 network.connectivity.port_check
-network.dns
-network.dns_assert
-network.dns_facts
+network.connectivity.port_wait
+network.dns.config
+network.dns.check
+network.dns.facts
 network.firewall.firewalld.forward_port
 network.firewall.firewalld.icmp_block
 network.firewall.firewalld.list
@@ -356,8 +356,6 @@ user.remove
 user.set_password
 user.shell_assert
 user.unlock
-wait.process
-wait.tcp
 ```
 
 ## Manuals by category

docs/plugins/linux-operations.md

@@ -65,11 +65,11 @@ pam.access / pam.faillock / pam.pwhistory / pam.succeed_if
 pam.service_line / pam.validate / pam.stack_facts / pam.authselect
 hosts.entry
 hostname.set
-network.dns
+network.dns.config
 chrony.servers / chrony.sources_assert
 ```
 
-`network.dns` is deliberately careful: with `backend: auto`, it refuses to
+`network.dns.config` is deliberately careful: with `backend: auto`, it refuses to
 replace a symlinked `/etc/resolv.conf` unless `force: true` or an explicit backend
 is provided. This avoids corrupting systems managed by systemd-resolved,
 NetworkManager, resolvconf or cloud-init.
@@ -108,9 +108,9 @@ structured `plan --diff` previews before applying storage changes.
 ## Runtime network operations
 
 Use `network.link.interface`, `network.link.bond`, `network.link.bridge`, `network.link.vlan`,
-`network.route.add`, `network.route.remove` and `network.dns` for runtime network setup
+`network.route.add`, `network.route.remove` and `network.dns.config` for runtime network setup
 and DNS resolver changes. DNS handling is
-backend-aware through the same safety rules as `network.dns`: managed or
+backend-aware through the same safety rules as `network.dns.config`: managed or
 symlinked resolver files are not overwritten silently.
 
 
@@ -187,7 +187,7 @@ Useful families include:
 
 ```text
 platform.facts
-network.dns_facts
+network.dns.facts
 network.link.facts / network.route.facts
 pkg.version_pin / pkg.repo_priority
 network.link.interface / network.link.bond / network.link.vlan / network.route.add / network.route.remove with persist/backend
@@ -224,7 +224,7 @@ existing configuration files.
 ## Network checks, facts and bridge operations
 
 Use `network.link.bridge` for explicit runtime bridge creation/removal. Use
-`network.link.check`, `network.route.check`, `network.dns_assert` and
+`network.link.check`, `network.route.check`, `network.dns.check` and
 `network.connectivity.port_check` as precheck/postcheck guards around network operations.
 Use `network.link.facts` and `network.route.facts` for read-only iproute2 JSON
 readback without treating mismatched state as a failed assertion.

docs/plugins/wait-assert.md

@@ -12,21 +12,21 @@ The public `assert.*` / `wait.*` surface is intentionally shrinking. File,
 directory and symlink checks now live in the type-specific filesystem families:
 `fs.dir.*`, `fs.file.*` and `fs.symlink.*`.
 
-## `wait.tcp` and `assert.tcp`
+## `network.connectivity.port_wait` and `network.connectivity.port_check`
 
-TCP checks run from the controller.
+Connectivity checks run from the remote target using `nc`.
 
 ```yaml
 - id: wait_port
-  use: wait.tcp
+  use: network.connectivity.port_wait
   with:
     host: "{{ server.host }}"
     port: 443
-    timeout: 60
+    retries: 30
     interval: 2
 
 - id: assert_port
-  use: assert.tcp
+  use: network.connectivity.port_check
   with:
     host: "{{ server.host }}"
     port: 443
@@ -53,13 +53,13 @@ wrong type. `*.wait` polls with `retries` and `interval`.
     path: /etc/myapp
 ```
 
-## `wait.process`
+## `process.wait`
 
 Waits for a remote process matching a pattern.
 
 ```yaml
 - id: wait_worker
-  use: wait.process
+  use: process.wait
   with:
     pattern: "myapp-worker"
     state: present

examples/runbooks/runbooks/04-assert.check.yaml

@@ -20,7 +20,7 @@ tasks:
         path: /tmp/automax-demo
         min_free_mb: 1
     - id: assert_tcp
-      use: assert.tcp
+      use: network.connectivity.port_check
       with:
         host: 127.0.0.1
         port: 22