chore: set binary name in config_2.yml #921
Merged
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.
Set custom binary name in
config_2.yml
to make usage of localspn
working when launchingspn
The reason for this is that the local
spn
instance and thespn
to launch could have different versionsIf cli interface is not compatible, usage of network command fails because the
spnd
command from thespn
to launch built binary will be run with the incompatible keyring of thespn
instance