You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bash scripts should be built ontop of the current scripts, since that has the correct path information as well as the environment variables exposed to them.
The text was updated successfully, but these errors were encountered:
It is not possible to provide a file outside of values.yaml file to the helm chart, hence simple genesis: scripts/setup_genesis.sh wont be able to work.
What we could do is, create a structure in which the user only provides the file name, and during the helm install command we use --set-file to set a data value into .Values, and create chain specific configmaps from that.
Default scripts can still be used.
This would require:
install.sh script to be used instead of helm install, so that we can parse helm to run the helm install commands properly
create configmaps for setup-scripts that is chain specific: {chain-name}-setup-scripts
NOTE: Leaning more and more to a custom config parser, that we want to expose to the users of Starship. Maybe the output of the parser can be a helm values.yaml file that we can use with our helm charts.
Use this concept for adding feature for adding $CHAIN_DIR with configmaps created from tar.gz files, which are mounted to the data dirs for the chains.
Size constraints for configmaps is 1MiB.
Optionally we need the ability to be able to pull the files from a link as well.
Overview
Currently all scripts being run inside the chain and relayers are default and available in the
scripts/
dir in the chart.Proposal
Make this customizable by pushing the scripts to the
values.yaml
The bash scripts should be built ontop of the current scripts, since that has the correct path information as well as the environment variables exposed to them.
The text was updated successfully, but these errors were encountered: