Can't set network alias upon container creation

When creating a container using client.containers.run(...) or client.containers.create(...) there doesn't seem to be a way to set a network alias for the container on its set network.
Setting an alias is possible when using a network's connect function, but upon creation some network is already attached to the container (default or otherwise) and will need to be detached if it is unnecessary.

What I am trying to do: run a container, attach it to a single custom network I created and set its alias so other containers on the same network can communicate with it.
This is possible to do using the CLI with --network-alias option, and also using the API with the networking_config structure, but based on file docker/models/containers.py line 1077 the SDK does not pass any special network configuration to the API besides the network name.

As far as I can tell the only way to achieve my desired state right now is to:

1. Run/create a container with default or w/e network
2. Connect custom network to container and set alias
3. Find container original network, client.networks.get() it and disconnect the container from it

Am I missing something or is this correct?
If it is correct - since the API allows this, can this be added? I can create a pull request if this need is agreeable.

Start in docker/models/containers.py at line 1077 and compare the SDK's container creation arguments with the Docker API's networking_config structure and the CLI's --network-alias option. Done means creating a container on a custom network with its network alias configured directly, without requiring a later connect and disconnect sequence.