fix: allow users to configure ISM with Opensearch #9866
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
Okhelifi
force-pushed
the
apim-7236-ism
branch
2 times, most recently
from
284eb2c
to
38da0e3
Compare
Okhelifi
force-pushed
the
apim-7236-ism
branch
2 times, most recently
from
9463cb5
to
d7c0648
Compare
Okhelifi
force-pushed
the
apim-7236-ism
branch
from
d7c0648
to
d1a4270
Compare
Okhelifi
force-pushed
the
apim-7236-ism
branch
from
d1a4270
to
ca9ac4a
Compare
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.
Issue
https://gravitee.atlassian.net/browse/APIM-7236
Description
Today when a customer tries to configure the ISM on opensearch it fails because of our templates.
Here is a PR to fix it.
Linked PR : gravitee-io/gravitee-reporter-elasticsearch#94
Additional context
📚 View the storybook of this branch here