Repository navigation
chore: remove Lava testnet deploy target - #18
Merged
Merged
Conversation
The Lava testnet (lava-testnet-2) is being sunset, so the indexer no longer offers a testnet deployment. - deploy.yml: testnet removed from the environment choice. The mainnet path (environment `mainnet`, task definition lava-indexer-mainnet-indexer) is unchanged. - ci.yml: push trigger no longer includes the testnet branch. - README: CI/CD section updated to match. Intentionally kept: indexer code and tests that mention testnet-2 (start-height handling, chain-id guard, multi-endpoint tests). That is generic chain logic and test data, not a testnet deployment. Not covered here (infra, handled separately): the GitHub `testnet` environment and its secrets, the lava-indexer-testnet ECS service and RDS instance, and testnet-indexer-status.lavanet.xyz.
nimrod-teich
marked this pull request as ready for review
November 10, 2026 09:33
nimrod-teich
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
The Lava testnet is being shut down. This repo offered a testnet deployment target for the indexer. After this change the deploy workflow is mainnet-only.
What changed
.github/workflows/deploy.yml:testnetremoved from theenvironmentchoice..github/workflows/ci.yml: push trigger no longer includes thetestnetbranch.README.md: CI/CD section updated to match.What is intentionally unchanged
mainnet, ECS task definitionlava-indexer-mainnet-indexer, same image tags.build.ymlandpublish.ymlhad nothing testnet-specific.lava-testnet-2(start-height handling, chain-id guard, multi-endpoint tests ininternal/rpc) stay. That is generic chain logic and test data, not a testnet deployment..env.examplecomment about naming compose stackslava-mainnet/lava-testnetstays; it is a generic example.Verification
go vet,go buildandgo test. The change touches no Go code.Not covered here (infra, handled separately after approval)
testnetand its secrets (AWS_ROLE_ARN).testnetgit branch (CI used to trigger on it).lava-indexer-testnetand its RDS instance (defined in the devops Terraform,components/lava-indexer/terraform/tfvars/testnet.tfvars). RDS keeps a final snapshot on destroy.testnet-indexer-status.lavanet.xyzDNS record.