-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Kava Protonet Data Reset Chain CI #2025
Conversation
…fferent tags and using autoscaling group for ordering
…h enteringStandby
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does a rebase onto master resolve the failing CI?
we probably shouldn't be updating kvtool in this PR
Nick's branch which then causes issues for ansible with:
but you're right, ideally we don't want any kvtool changes here, but this was the branch I needed to test since it's not in master yet. |
setting to draft to triple check quality |
description
autoscaling groups
to be ran forkava-node-updater
since new infra doesn't useKavaChainId
and usesChainId
and this is to ensure we reset the validator node first then any api nodes afterwardskava protonet genesis contains all the necessary fields set
This flow will be removed eventually for testnetV2
Description
Checklist