What problem does your feature solve?
if you want to install the helm chart for core on testnet or pubnet, there is no reference values.yml to use, which aggregates many specific settings needed for network like validators, passphrase, archive urls, etc. it would take a long time and be error prone to try and set that up manually.
What would you like to see?
testnet_values.yml and pubnet_values.yml are created in the core chart path to be usable in helm install --values.
Or global.network=[testnet|pubnet] works the same and prevents need for testnet_values.yml and pubnet_values.yml .
updated docs can refer to correct config - stellar/stellar-docs#216
What alternatives are there?
users take the futurenet_values.yml and manually figure out the changes from there for testnet or pubnet.
What problem does your feature solve?
if you want to install the helm chart for core on testnet or pubnet, there is no reference values.yml to use, which aggregates many specific settings needed for network like validators, passphrase, archive urls, etc. it would take a long time and be error prone to try and set that up manually.
What would you like to see?
testnet_values.ymlandpubnet_values.ymlare created in the core chart path to be usable inhelm install --values.Or
global.network=[testnet|pubnet]works the same and prevents need fortestnet_values.ymlandpubnet_values.yml.updated docs can refer to correct config - stellar/stellar-docs#216
What alternatives are there?
users take the futurenet_values.yml and manually figure out the changes from there for testnet or pubnet.