Added proxy information to plugin configuration #4010
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.
Hi all!
With this PR, I'm proposing my idea to add a couple of the information to the proxy during the plugin configuration.
Inside my test to develop a new plugin, I noted the necessity to know if the node has the proxy enabled, the solution was to add a plugin option but I think this is redundant propriety during the node setup!
Another solution is to use the
listconfigs
to set up the connection inside the plugin but in some cases the method plugin call before to start some plugin methods! For instance, an alternative backend bitcoin/element that overrides the pluginbcli
I hope that I'm losing nothings.