chore(web, api, worker): Remove multi-provider feature flag #4396
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
NV-2907 Remove the IS_MULTI_PROVIDER_CONFIGURATION_ENABLED feature flag
What?We would like to remove the Why? (Context)The feature flag Definition of Done
|
|
This PR has been split into 2: |
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.
What change does this PR introduce?
This PR removes the multi-provider feature flag from the Web, Worker, and API packages. It also adds documentation to support new users to get started with local API development.
Why was this change needed?
The multi-provider feature has been successfully implemented in production for an adequate length of time.
Other information (Screenshots)
The following redundant use-cases have been removed:
DeactivateSimilarChannelIntegrationsDisableNovuIntegration