-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
processing_configuration not available for AWS Splunk Firehose Delivery Stream #5054
Comments
Hi @cwiggs 👋 Sorry you're running into trouble here. I am presuming this issue is a continuation of #3944 (comment), on the merged pull request that added the functionality requested here. In that comment you mention:
There's two possibilities that we can easily check:
We explicitly acceptance test this functionality daily without issue, using this test configuration: https://github.com/terraform-providers/terraform-provider-aws/blob/867b227ca892f5d609cf721651a92e20e439b45c/aws/resource_aws_kinesis_firehose_delivery_stream_test.go#L1751-L1798 Please let us know, thanks. |
You are correct! Let me submit a fix to the documentation. Here we go: #5102 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
Should be able to define lambda transformer for Splunk destination the same way a processor can be defined for extended s3 destinations.
New or Affected Resource(s)
Potential Terraform Configuration
References
Same issue for elasticsearch: #2729
The text was updated successfully, but these errors were encountered: