Deploy/undeploy bundled RVD through configuration #2351
Merged
Conversation
This file contains hidden or 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
- RVD will get either deployed or undeployed based on the value of advanced.conf/RVD_URL Refers #2350
|
@lefty, i've provided a fix that makes sure RVD is not deployed when restcomm first starts. |
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.
Added configuration in restcomm-config.sh that controls whether RVD is deployed or not based on the RVD_URL parameter in advanced.conf. By default (RVD_URL is empty) it will get deployed.
Currently, this PR will make no difference to a a restcomm installation. In an RVD microservice setup when RVD_URL will point to a remote RVD, the bundled version will get undpeloyed.
Refers to #2350