bug: Setting relaxed-security in config file doesn't seem to work

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I start the Appium server with this config yaml:

server:
  base-path: /wd/hub
  keep-alive-timeout: 800
  relaxed-security: true
  use-plugins:
    - device-farm
    - appium-dashboard
  plugin:
    device-farm:
      platform: android

I run appium --config /path/to/my/config. The documentation tells me to use --config-file, however that argument doesn’t seem to work, whereas --config works. The server starts like this:

[Appium] Welcome to Appium v2.0.0-beta.44
[Appium] Non-default server args:
[Appium] {
[Appium]   basePath: '/wd/hub',
[Appium]   keepAliveTimeout: 800,
[Appium]   usePlugins: [
[Appium]     'device-farm',
[Appium]     'appium-dashboard'
[Appium]   ]
[Appium] }

Relaxed-security seems to be missing and when I do shell commands, it notifies me that I have to allow-insecure adb_shell. However if I start the server with the flag: appium --relaxed-security --config /path/to/my/config it looks correct:

[Appium] Welcome to Appium v2.0.0-beta.44
[Appium] Non-default server args:
[Appium] {
[Appium]   basePath: '/wd/hub',
[Appium]   keepAliveTimeout: 800,
[Appium]   relaxedSecurityEnabled: true,
[Appium]   usePlugins: [
[Appium]     'device-farm',
[Appium]     'appium-dashboard'
[Appium]   ]
[Appium] }

I tried this with a json also. Any ideas?

Expected Behavior

Setting the boolean value relaxed-security: true inside the config should enable this feature and notify me inside the Appium Log.

Minimal Reproducible Example

Start the Appium server using a JSON or YAML config with the argument relaxed-security: true

Environment

• Operating system: Windows 10
• Appium 2.0.0-beta.44
• Appium driver(s) and their version(s): Espresso Driver 2.13.8
• Appium plugin(s) and their version(s): Appium-Dashboard 1.10 + Device-Farm 3.4.0

Link to Appium Logs

No response

Futher Information

No response

[boneskull]

@ValzRon OK, we’ve published; please update and try again

[ValzRon]

@ValzRon OK, we’ve published; please update and try again

This works, thank you!