Identify deployed instances to separate production from dev #53
Conversation
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
data and data from other sources (eg. synthetic)
thompson318
reviewed
Feb 9, 2026
Collaborator
thompson318
left a comment
thompson318
left a comment
There was a problem hiding this comment.
Looks like a good way of differentiating between data to address the issue. A few comments/questions to think about.
jeremyestein
had a problem deploying
to
hasher
GitHub Actions
Failure
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.
Implements #42
Each deployed instance now needs to be given a name so its outputs can be identified. To prevent, for example, synthetic data on the DSH from being mixed up with production data.
The name is configured in the exporter.env file.
It is output in: