Dynamic connection properties retrieval #7386
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
* Adding a new method in the MetadataRetrieval interface to allow any Connector to expose a list of dynamic properties * Fixing a few unit test that were not using getter accessor method Closes ENTESB-12482
* Exposing a POST endpoint to retrieve dynamic properties on any connector * Refactor connector-support-verifier * Added unit test Closes ENTESB-12481
* Exposing a POST endpoint to retrieve dynamic properties Closes ENTESB-12480
|
@squakez The bot could not transition the ticket automatically, please update this Jira ticket manually: https://issues.redhat.com/browse/ENTESB-12498 |
squakez
added
group/connector
Delawen
approved these changes
Dec 12, 2019
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.
Goal of this PR is to expose a REST API that will be used by connection user interface to dynamically expose any connection property that can be retrieved dynamically by the connector.
During this first iteration I am leaving aside the resiliency of the meta http call from server: it will be provided during a following iteration (ENTESB-12498)
Originally required by #2828
Needed to enable product feature ENTESB-11952