Closed tbruyelle closed 1 year ago
LGTM, I will wait for the comments to be resolved before approving 👍
Good to merge! nice
If possible, it's better to merge https://github.com/ignite/cli/pull/3306 first because then we can use a hash from cli@main in the plugin go.mod.
If possible, it's better to merge ignite/cli#3306 first because then we can use a hash from cli@main in the plugin go.mod.
Forget about that, we'll have to set the plugin version also in cli
, and we have to do that after the merge of this PR, so let's do that first.
import StartProxyForTunneledPeers from CLI
Hi, is this advice valid? I tried to search both in cli and cli-plugin-network repos for StartProxyForTunneledPeers
in the codebase but it can't be found anywhere.
I'm upgrading ignite/cli from 25->26 and not sure what to do with network.StartProxyForTunneledPeers
in a scaffolded app given that github.com/ignite/cli/ignite/services/network
is removed.
This PR imports the network code from CLI with a couple of changes :
network tool proxy-tunnel
that replaces thestart-with-tunneling-command
(removed from scaffolded chain)network chain prepare
to callnetwork tool proxy-tunnel
beforeappd start
.ignitecmd
package renamed tocmd
StartProxyForTunneledPeers
from CLITo use this plugin, just compile
ignite
from https://github.com/ignite/cli/pull/3306 and runignite network
.The code has been updated regularly thanks to patches, so it should be up-to-date with
CLI/main
but it's better to have a closer look on that.