Use faraday 1.x explicitly #71
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
opensearch-transport 2.0.1 and 1.0.1 unlocks using faraday 2.x but fluent-plugin-opensearch isn't ready for it, as a result out_opensearch doesn't work on newly install. Fix #70 Signed-off-by: Takuro Ashie <ashie@clear-code.com>
|
I tried faraday 2.x too but CI for ruby 2.x failed: |
|
Oh, I didn't notice about it. Looks good. |
cosmo0920
approved these changes
Aug 9, 2022
|
I'd released this change as v1.0.8. 💪 |
2 tasks
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.
opensearch-transport 2.0.1 and 1.0.1 unlocks using faraday 2.x but
fluent-plugin-opensearch isn't ready for it, as a result out_opensearch
doesn't work on newly install.
Fix #70
Signed-off-by: Takuro Ashie ashie@clear-code.com
DESCRIPTION HERE
(check all that apply)
versionin gemspec are untouched