--network is ignored when --host is used

[ryokik]

If --host is specified, --network is ignored, so nothing can be deployed with the flow deploy command.

Steps to reproduce

1. clone https://github.com/ryokik/example-flow-project (or flow setup and add some contracts)
2. Start emulator flow emulator
3. Deploy contracts with host option flow deploy --host 127.0.0.1:3569 --network emulator

Additional Info

I am using jest for automated testing.
I use a different port than usual to run emulator in parallel.

Looking at the implementation, it appears that when host is specified, the internal name is "custom".

flow-cli/internal/command/command.go

Line 204 in daa1550

return &config.Network{Name: "custom", Host: hostFlag, Key: networkKeyFlag}, nil

[ryokik]

Also, when '--host' is specified, references (imports) between contracts cannot be resolved.
This also seems to be caused by the fact that the network name is internally set to "custom".

[sideninja]

You are right, but I wonder if you think this is a issue? the way I was thinking about is, if you have a custom host for a network you would define that in "networks" section in flow.json and then just use that network name on the deploy.

[ryokik]

I run flow emulators in parallel for automated testing.
Each has a different port: 127.0.0.1:3569, 127.0.0.1:3570, 127.0.0.1:3571 ...

When --network flag is used, I have to define networks like emulator-1, emulator-2, emulator-3, and the same number of duplicate deployments.