-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document that pipeline
needs to be lowercase
#42438
Merged
belimawr
merged 1 commit into
elastic:main
from
belimawr:41224-document-pipeline-lowercase
Jan 28, 2025
Merged
Document that pipeline
needs to be lowercase
#42438
belimawr
merged 1 commit into
elastic:main
from
belimawr:41224-document-pipeline-lowercase
Jan 28, 2025
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
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names.
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
mauri870
approved these changes
Jan 28, 2025
mergify bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jan 28, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86)
6 tasks
belimawr
added a commit
that referenced
this pull request
Jan 30, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
belimawr
added a commit
that referenced
this pull request
Jan 30, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
belimawr
added a commit
that referenced
this pull request
Jan 30, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
belimawr
added a commit
that referenced
this pull request
Jan 31, 2025
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names. (cherry picked from commit 8406c86) Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-8.x
Automated backport to the 8.x branch with mergify
backport-8.16
Automated backport with mergify
backport-8.17
Automated backport with mergify
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
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.
Proposed commit message
Document that the ingest pipeline ID from Elasticsearch defined in the input or output configuration is always lowercased, thus the ingest pipeline in Elasticsearch can only use lowercase names.
Checklist
My code follows the style guidelines of this projectI have commented my code, particularly in hard-to-understand areasI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.## Disruptive User Impact## Author's ChecklistHow to test this PR locally
beats
anddocs
have the same parent folder$GIT_HOME
as the parent folder frombeats
anddocs
Related issues
pipeline
the name is always lowercased #41224## Use cases## Screenshots## Logs