feat: connector multidc on alert engine connection #969
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
|
Kudos, SonarCloud Quality Gate passed!
|
ghost
approved these changes
Jan 11, 2023
AndrewMcFarlandCampbellGravitee
approved these changes
Jan 11, 2023
marcambier
approved these changes
Jan 11, 2023
ghost
added
the
passionne
reviewed
Jan 19, 2023
passionne
approved these changes
Jan 19, 2023
remisultan
force-pushed
the
ae-connector-2.1.0
branch
from
768f1d0 to
b53bfe5
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
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/AE-46
Description
This PR describes how to configure the Alert Engine connector to connect to multiple unrelated clusters
Additional context
We need to wait until APIM/AM include the changes before merging
🚀 CI was able to deploy the build of this PR, so you can now try it directly here