Feat (Deployment): Support custom binaries #45
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
OjusWiZard
force-pushed
the
feat/custom-binary-deployment
branch
from
b348662 to
ce38969
Compare
|
How is the binary path sent to the mw from cli? |
|
@jmoreira-valory Right now it's expected in the service template, with field "binary_path". If it's not provided then the QS will default back to docker deployment. |
OjusWiZard
force-pushed
the
feat/custom-binary-deployment
branch
from
ce38969 to
38a0881
Compare
Signed-off-by: OjusWiZard <[email protected]>
OjusWiZard
force-pushed
the
feat/custom-binary-deployment
branch
from
38a0881 to
7139f31
Compare
Signed-off-by: OjusWiZard <[email protected]>
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.
Proposed changes
Types of changes
What types of changes does your code introduce?
Put an
xin the boxes that apply