dashpay / platform

L2 solution for seriously fast decentralized applications for the Dash network
https://dashplatform.readme.io/docs/introduction-what-is-dash-platform
MIT License
67 stars 39 forks source link

bug(dashmate): `config set <key> null` sets to string value of "null" #1343

Closed strophy closed 1 day ago

strophy commented 1 year ago

Expected Behavior

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

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

shumkov commented 1 day ago

This is fixed.