[tooling] Improve local ecosystem management - #1706
Merged
BenjaminPelletier merged 3 commits intoSep 15, 2026
Merged
Conversation
BenjaminPelletier
marked this pull request as ready for review
September 12, 2026 06:40
barroco
approved these changes
Sep 13, 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
2 participants
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.
Somewhat recently, we added powerful new features to deploy a local ecosystem (especially a pool of DSS instances) with a number of configuration parameters, especially NUM_USS, NUM_NODES, and DB_TYPE. One new problem this introduced is that a local ecosystem needed to be turned down from the same shell (or with the same environment variables) that brought it up. Keeping track of environment variables relative to local ecosystem state can be challenging. In addition, there was little visual feedback indicating the nature of the local ecosystem that was just deployed. This PR addresses these challenges by improving local ecosystem management to print information about the ecosystem being deployed, and automatically detecting the important variables needed to shut down whatever local ecosystem is currently running regardless of environment variables.