Adding a license cluster command #116
Merged
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
hoenn
reviewed
Nov 7, 2024
|
Should be able to write a test for this new functionality. |
|
@hoenn I plan to, I'm just pulling it together to start getting eyes on them. 👀 |
antkaynak
approved these changes
Nov 20, 2024
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.
In order to securely add licensing to our Elasticsearch clusters I have added LicenseCluster action. This action takes in a string containing the json license and applies it to the cluster.
This is just one component that will be used in the licensing workflow from
vulcan-go.Tracking issue here: https://github.com/github/elasticsearch/issues/4211