feat(elasticsearch): add an Elasticsearch 7.10.2 cluster on staging #887
Conversation
This file contains 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
…eir role Whether an existing or new Elasticsearch cluster will act as the primary or secondary cluster is subject to change over time. Therefore, clusters shouldn't have their current role reflected in their permanent name. I chose to start naming them after bees, starting with the honey bee.
tarrow
approved these changes
May 12, 2023
There was a problem hiding this comment.
looks fine to me; definitely happier using something other than primary for this new cluster. Using bee names is totally fine to me too and somewhat humorous; hopefully we don't get confused by this in the future; if we do I suggest moving to including the version number (or even just integers) in the name.
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.
No description provided.