Running dashmate config set platform.dapi.envoy.ssl.providerConfigs.zerossl.id null should set the value to a JSON null as defined in the schema.
Current Behavior
Instead, somehow it gets set to the string "null" instead, breaking dashmate on next run.
dashmate@hp-masternode-17:~$ dashmate config set platform.dapi.envoy.ssl.providerConfigs.zerossl.id null
platform.dapi.envoy.ssl.providerConfigs.zerossl.id set to null
dashmate@hp-masternode-17:~$ dashmate config get platform.dapi.envoy.ssl.providerConfigs.zerossl.id
InvalidConfigFileFormatError: Invalid
'/home/dashmate/.dashmate/config.json' config format: co
nfig/platform/dapi/envoy/ssl/providerConfigs/zerossl/id
must NOT have fewer than 32 characters
Expected Behavior
Running
dashmate config set platform.dapi.envoy.ssl.providerConfigs.zerossl.id null
should set the value to a JSONnull
as defined in the schema.Current Behavior
Instead, somehow it gets set to the string
"null"
instead, breaking dashmate on next run.Possible Solution
Steps to Reproduce (for bugs)
1. 2. 3. 4.
Context
Trying to set ZeroSSL API key ID in deploy tool to avoid incorrectly indicating the template changed https://github.com/dashpay/dash-network-deploy/pull/537
Your Environment