Philip Obiora

@quest-bot loot #1051

Alright, i will do that

> mirror behaviour of tools like kubectl to allow users to pipe JSON directly into the command via stdin `cat config.json | daytona target set --stdin` so the command should...

> @Philip-21 let;s ensure that the options provided by users align with what each provider expects. > > Here's a breakdown of the steps: > > * [ ] Fetch...

> @Philip-21 ensuring that the `options` provided by users align with each provider's expectations is crucial for the reliability of the `daytona target set` command. > > **Validating User-Provided JSON...

Hello @mojafa , @Tpuljak i have implemented the commands ``` daytona target set -f /path-to-json cat /pathtojson/ | daytona target set -f - ```

> **Validating User-Provided JSON Options** focus on both `key names` and `values`: > > * Ensure that all keys in the JSON match exactly with those defined in the provider's...

### Docker  the above is an invalid key name in the options field `sockPath`, its mean to be Sock Path  The above is a valid docker target setup...

### GCP  Here, i tested out validating the key names and values, observe the errors returned based on these validations

Here are the list of my targets, i ensured the Key names and values are correct based on the [daytona docs](https://www.daytona.io/docs/configuration/targets/#docker-local)