ci: update internal testnet reset workflow #2035
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates CD pipeline for internal testnet, now on newer infra. The action uses the same workflows as the protonet flow, but with different variables.
Confirmed the reset + seeding of network works by running the workflow locally.
Additionally, removed all workflows and scripts that are no longer used.
The workflow is triggered in either of these cases:
ci/kava-internal-testnet
have changednote the above differs from protonet, which deploys on any commit to master. even with
KAVA.VERSION
pinned tomaster
, the network will not redeploy on new commits because the files inci/kava-internal-testnet
will not change. if the commit is updated or the genesis file changes, the network will be reset & deployed. otherwise, the network will only be reset if the workflow is manually dispatched.