Environment parity connector spike #201
Draft
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This adds a second APIM connector,
APIMConnectorEnvironmentParityImpl, although it's just a skeleton implementation. This could use different configuration than the existing connector.In
application.confthere is a new configuration value,features.environment-parity. This is used byModuleto determine which connector implementation should be used at runtime. We could therefore switch implementation by updating this value in an environment configuration file such asapp-config-qaand redeploying.A controller,
EnvironmentParityTestController, has been added that explicitly usesAPIMConnectorEnvironmentParityImpland could test our connectivity to new APIM environments via the platform API while existing code uses the original connector.