Update Logstash pipeline create example. #1335
Closed
+2
−2
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
|
@tobio sorry for direct ping... I don't know honestly who would be the best person to review my this small change but I would appreciate if you take a look and review. Thank you! |
tobio
reviewed
Sep 27, 2025
| } | ||
| output "pipeline" { | ||
| value = elasticstack_elasticsearch_logstash_pipeline.example.pipeline_id |
There was a problem hiding this comment.
This is just referencing the pipeline_id of the resource declared above which does comply with the validation rules.
|
@mashhurs the example here meets the validation rules, with |
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.
Kibana and Elasticsearch APIs start validating pipeline IDs after the following changes:
The
examples/resources/elasticstack_elasticsearch_logstash_pipeline/resource.tfexample will not be valid anymore.This PR updates the example to align with pipeline ID restriction changes.