This repository has been archived by the owner on May 16, 2023. It is now read-only.
[elasticsearch] remove usage of ELASTIC_USERNAME #1506
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
This commit remove the usage of ELASTIC_USERNAME and replace it by hardcoded "elastic" username. This is required because ELASTIC_USERNAME don't seem to be supported anymore supported by Elasticsearch (I couldn't find the exact version where support was stopped).
|
transient issues, merging |
jmlrt
added a commit
to jmlrt/helm-charts
that referenced
this pull request
Dec 20, 2021
This commit remove the usage of ELASTIC_USERNAME and replace it by hardcoded "elastic" username. This is required because ELASTIC_USERNAME don't seem to be supported anymore supported by Elasticsearch (I couldn't find the exact version where support was stopped).
jmlrt
added a commit
to jmlrt/helm-charts
that referenced
this pull request
Dec 20, 2021
This commit remove the usage of ELASTIC_USERNAME and replace it by hardcoded "elastic" username. This is required because ELASTIC_USERNAME don't seem to be supported anymore supported by Elasticsearch (I couldn't find the exact version where support was stopped).
jmlrt
added a commit
that referenced
this pull request
Dec 20, 2021
This commit remove the usage of ELASTIC_USERNAME and replace it by hardcoded "elastic" username. This is required because ELASTIC_USERNAME don't seem to be supported anymore supported by Elasticsearch (I couldn't find the exact version where support was stopped).
jmlrt
added a commit
that referenced
this pull request
Dec 20, 2021
This commit remove the usage of ELASTIC_USERNAME and replace it by hardcoded "elastic" username. This is required because ELASTIC_USERNAME don't seem to be supported anymore supported by Elasticsearch (I couldn't find the exact version where support was stopped).
This was referenced Dec 20, 2021
Merged
Merged
This was referenced Sep 14, 2022
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This commit remove the usage of ELASTIC_USERNAME and replace it by
hardcoded "elastic" username.
This is required because ELASTIC_USERNAME don't seem to be supported
anymore supported by Elasticsearch (I couldn't find the exact version
where support was stopped).
This was already done as part of #1384 in the main branch.