Merge pull request #379 from VirtualMetric:DT-543-manual-update-documentation

DT-543-Add Updates documentation page for Directors

Author: KorayErkan

docs/configuration/directors/management.mdx

@@ -308,111 +308,6 @@ Directors with connected devices or agents cannot be deleted. The error modal li
 3. Reassign agents to different Director or delete
 4. Retry Director deletion after dependencies removed
 
-## Auto Update
-
-Auto Update enables Directors to automatically update themselves when new versions become available. The feature supports immediate and scheduled update methods with built-in rollback capability and cryptographic signature verification.
-
-### Configuration
-
-Auto Update is configured through the `update` section in the Director configuration:
-
-| Property | Type | Required | Description |
-|---------:|:-----|:--------:|:------------|
-| mode | string | Y | Set to `auto` to enable automatic updates |
-| method | string | Y | Update trigger method: `immediate` or `schedule` |
-| version | string | Y | Target version to update to |
-| cron | string | N | Cron expression for scheduled updates (schedule method only, minimum 30 seconds) |
-| interval | duration | N | Fallback polling interval if no cron specified (default: 30s minimum) |
-
-**Example Configuration:**
-
-```yaml
-update:
-  mode: auto
-  method: schedule
-  version: "2.5.0"
-  cron: "0 2 * * 0"  # Every Sunday at 2:00 AM
-```
-
-### Update Methods
-
-**Immediate Method:**
-
-Triggers the update as soon as possible after configuration is applied. A 10-minute cooldown prevents rapid retry attempts if the update fails.
-
-```yaml
-update:
-  mode: auto
-  method: immediate
-  version: "2.5.0"
-```
-
-**Schedule Method:**
-
-Updates occur according to a cron schedule or interval-based polling:
-
-- **Cron Expression**: Use standard cron syntax for precise scheduling (e.g., `0 2 * * 0` for Sunday at 2:00 AM)
-- **Interval Fallback**: If no cron is specified, updates check on the configured interval
-
-```yaml
-update:
-  mode: auto
-  method: schedule
-  version: "2.5.0"
-  interval: 1h  # Check hourly
-```
-
-### Update Process
-
-When an update triggers, the Director performs these steps:
-
-1. **Version Check** - Compares current version against configured target version
-2. **Service Stop** - Gracefully stops the running Director service
-3. **Backup** - Creates timestamped backup of current binary and configuration
-4. **Download** - Retrieves new binary from Fleet management instance
-5. **Signature Verification** - Verifies Ed25519 signature of downloaded binary
-6. **Deployment** - Replaces current binary with new version
-7. **Resource Update** - Updates package resources (pipelines, definitions)
-8. **Service Start** - Restarts the Director service
-
-If any step fails, the rollback system automatically restores the previous binary and configuration.
-
-### Health Reporting
-
-During an update, the Director reports additional health information:
-
-| Field | Description |
-|------:|:------------|
-| version | Currently running Director version |
-| scheduled_version | Target version pending update |
-| architecture | System architecture (amd64, arm64, etc.) |
-| os | Operating system (windows, linux, darwin) |
-
-The scheduled version field appears in health reports after an update is triggered but before it completes, allowing monitoring systems to track pending updates.
-
-### Update Logs
-
-Update progress is logged to the Director activity stream. Log entries include:
-
-- Update triggered timestamp
-- Download progress and completion
-- Signature verification result
-- Deployment success or failure
-- Rollback actions (if update fails)
-
-### Security
-
-Auto Update includes multiple security measures:
-
-- **Ed25519 Signature Verification**: All downloaded binaries are verified against cryptographic signatures before deployment
-- **Secure Download**: Binaries are downloaded over HTTPS from the Fleet management instance
-- **Rollback Protection**: Failed updates automatically restore the previous working version
-- **Path Traversal Protection**: Archive extraction validates paths to prevent directory escape
-
-:::warning
-Auto Update requires network connectivity to the Fleet management instance. Ensure firewall rules allow outbound HTTPS connections to the configured Fleet instance URL.
-:::
-
 ## Agent Pre-Processing
 
 Directors can configure Agents to perform pipeline-based pre-processing of logs before transmission. This distributed processing model reduces Director workload, decreases network bandwidth consumption, and enables edge-based data transformation such as compliance masking.