🐞 [Bug]: The Most Applications don't have a Wireguard Network option

[atefnazmy]

Is there an existing issue for this?

• [X] I have searched the existing issues

which package/s did you face the problem with?

Dashboard

What happened?

• The most applications don't have a Wireguard Network option.

Steps To Reproduce

No response

which network/s did you face the problem on?

Dev

version

ac03039

Twin ID/s

No response

Node ID/s

No response

Farm ID/s

No response

Contract ID/s

No response

Relevant screenshots/screen records

Relevant log output

n/a

[Mahmoud-Emad]

Issue update

Changes

• Enabled the Public IPv4 and displayed it as a 'read-only' field

• Send the value of the 'Wireguard' option to the deployment

• Updated the return of the 'createWorker' function to be ready to accept all networks

• Updated the worker interface to accept all networks

• Infrared the type of the name in the validator to avoid typescript errors

• Send the value of the 'Wireguard' to the deployment

• Enable Mycelium option by default

• Added the Wireguard option to the K8S deployment

• Added a watcher into all solutions that require a domain to be deployed to watch on the custom domain value then updated the Wireguard option

• Added a new attr 'read-only' in the 'Networks' component to set the 'Wireguard' option as 'read-only'

• Update the opacity of the 'Wireguard Switch' in the 'Networks' component

• Updated all applications with the new requirement and tested the full workflow

Proposal

• https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3294

[Mahmoud-Emad]

• Established a new constant by computing the options for IPv4 and custom domains to decide whether the Wireguard option should be read-only or not.
• Monitored the 'isWireguardReadonly' constant to determine the value of the Wireguard feature based on it.

[A-Harby]

Verified, Devnet 99b5130.

The wiregurad option is added to all of the solutions: VMs, Orchestrators and Applcations.