Parameterized Testnet #59
Conversation
| @@ -0,0 +1,36 @@ | |||
| # Stride Node Setup | |||
| @@ -0,0 +1,71 @@ | |||
| { | |||
| "version": 4, | |||
There was a problem hiding this comment.
curious if we need to check in tfstate or if terraform state pull suffices? no problem at all with checking it in, just wondering what happens if two people run terraform commands without checking it in (could we end up in a bad state?)
There was a problem hiding this comment.
great question. Honestly, I think the best practice would be to store the state using a terraform cloud account. It's free and pretty easy to setup.And to the second question, I think it will error out if we try and run a command from an outdated state - not positive though.
One thing to talk through today might be how we separate out different deployments. I'm hoping just the variable change acts as the equivalent of having a main.tf if an entirely different file (in that it treats them as separate terraform modules/resources) - but definitely something to double check
| $st_cmd init $moniker --chain-id $CHAIN_NAME --overwrite 2> /dev/null | ||
|
|
||
| # Update node networking configuration | ||
| sed -i -E "s|cors_allowed_origins = \[\]|cors_allowed_origins = [\"\*\"]|g" "${STATE}/${node_name}/config/config.toml" |
There was a problem hiding this comment.
good flag on this yesterday, will see if we can restrict this to only stridenet.co
Update validator.network seed node addresses
Summary
Test plan