[Bug] Service stuck and cannot be deleted

[docimin]

Stacktrace

https://gist.github.com/docimin/070dc2d68b439aa657ad7726d0ea4ef5
https://gist.github.com/docimin/92e120cc70398f5fe811ae0d25731b53

Actions to reproduce

• Make a task via the "Creates a task" API (api/v2/documentation/index.html#post-/task) using the "Fill Example"
• Service won't start, task keeps spamming because the URL is not valid
• Delete the task
• Delete the service

Deleting the service is not possible, and it will get stuck on "Not connected" [07.07 20:13:07.663] INFO: | Lobby-1 | PREPARED | IPADDRESS:25565 | Node-1 | Not connected

CloudNet version

[07.07 20:02:01.451] INFO:
[07.07 20:02:01.452] INFO: CloudNet Blizzard 4.0.0-RC9-SNAPSHOT f3c4cdbd
[07.07 20:02:01.452] INFO: Discord: <https://discord.cloudnetservice.eu/>
[07.07 20:02:01.452] INFO:
[07.07 20:02:01.452] INFO: ClusterId: 10f3b547-****-47b9-****-4242a50a736f
[07.07 20:02:01.453] INFO: NodeId: Node-1
[07.07 20:02:01.453] INFO: Head-NodeId: Node-1
[07.07 20:02:01.453] INFO: CPU usage: (P/S) .17/5.09/100%
[07.07 20:02:01.453] INFO: Node services memory allocation (U/R/M): 1024/1024/128014 MB
[07.07 20:02:01.454] INFO: Threads: 41
[07.07 20:02:01.454] INFO: Heap usage: 62/256MB
[07.07 20:02:01.454] INFO: JVM: Private Build 17 (OpenJDK 64-Bit Server VM 17.0.7+7-Ubuntu-0ubuntu122.04.2)
[07.07 20:02:01.454] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: nightly
[07.07 20:02:01.455] INFO:

Other

The "Lobby" task the example fills: https://just-paste.it/5RF4mSiihw/

Issue uniqueness

• [X] Yes, this issue is unique. There are no similar issues.

[0utplay]

The example in the documentation is not correct. Dont forget to add a includes list (like excludes) to the deployments segtion

[docimin]

The example in the documentation is not correct. Dont forget to add a includes list (like excludes) to the deployments segtion

So something like this? https://gist.github.com/docimin/df69b3c5ec670ef34440ebc345960f24

[0utplay]

Besides the fact that the values probably won't work the schema is correct.