[GH-ISSUE #269] Update the Servers Collection to Support Tailscale Connectivity #180

Closed
opened 2026-03-03 11:13:36 +03:00 by kerem · 1 comment
Owner

Originally created by @manikanta9176 on GitHub (Jun 25, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/269

Originally assigned to: @manikanta9176 on GitHub.

  • Add a new field preferConnectionType to specify the preferred connection method: either ssh or tailscale.

  • This field indicates preference, not exclusivity. Based on the selected preferConnectionType:

    • If tailscale is selected:

      • All Tailscale-related fields must be required.
      • SSH fields may still be filled, but are not required.
    • If ssh is selected:

      • All SSH-related fields must be required.
      • Tailscale fields may still be filled, but are not required.
  • Implement this conditional validation in both:

    • Frontend (e.g., using form schema validation with Zod or Yup)
    • Backend (e.g., using Payload CMS hooks like beforeValidate or beforeChange)
Originally created by @manikanta9176 on GitHub (Jun 25, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/269 Originally assigned to: @manikanta9176 on GitHub. * Add a new field `preferConnectionType` to specify the preferred connection method: either `ssh` or `tailscale`. * This field indicates preference, not exclusivity. Based on the selected `preferConnectionType`: * If `tailscale` is selected: * All **Tailscale-related fields must be required**. * **SSH fields may still be filled**, but are not required. * If `ssh` is selected: * All **SSH-related fields must be required**. * **Tailscale fields may still be filled**, but are not required. * Implement this conditional validation in both: * **Frontend** (e.g., using form schema validation with Zod or Yup) * **Backend** (e.g., using Payload CMS hooks like `beforeValidate` or `beforeChange`)
kerem 2026-03-03 11:13:36 +03:00
Author
Owner

@manikanta9176 commented on GitHub (Jun 25, 2025):

Note on Field Requirements:

  • For SSH-related fields: All fields are required except for hostname.

  • For Tailscale-related fields:

    • The following fields are required initially: name, description, hostname, and username.
    • Additional fields like publicIp and other connection details may be populated after the machine is successfully connected to Tailscale.
<!-- gh-comment-id:3003999077 --> @manikanta9176 commented on GitHub (Jun 25, 2025): **Note on Field Requirements:** * For **SSH-related fields**: All fields are required **except** for `hostname`. * For **Tailscale-related fields**: * The following fields are required initially: `name`, `description`, `hostname`, and `username`. * Additional fields like `publicIp` and other connection details may be populated **after the machine is successfully connected to Tailscale**.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dflow#180
No description provided.