docs(rust): update tcp-inlet create usages on command examples

examples/command/portals/ai/amazon_ec2/aws_cli/health_corp/run_ockam.sh

@@ -34,6 +34,6 @@ ockam project enroll "$ENROLLMENT_TICKET"
 # This makes the remote AI API available on all localhost IPs at - 0.0.0.0:3000
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.ai-outlet "true")'
-ockam tcp-inlet create --from 0.0.0.0:3000 --to ai
+ockam tcp-inlet create --from 0.0.0.0:3000 --via ai
 
 EOS

examples/command/portals/apis/nodejs/amazon_ec2/aws_cli/travel_app_corp/run_ockam.sh

@@ -34,6 +34,6 @@ ockam project enroll "$ENROLLMENT_TICKET"
 # This makes the remote postgres available on all localhost IPs at - 0.0.0.0:3000
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.monitoring-api-outlet "true")'
-ockam tcp-inlet create --from 0.0.0.0:3000 --to monitoring-api
+ockam tcp-inlet create --from 0.0.0.0:3000 --via monitoring-api
 
 EOS

examples/command/portals/databases/postgres/amazon_aurora/aws_cli/analysis_corp/run_ockam.sh

@@ -34,6 +34,6 @@ ockam project enroll "$ENROLLMENT_TICKET"
 # This makes the remote postgres available on all localhost IPs at - 0.0.0.0:15432
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.postgres-outlet "true")'
-ockam tcp-inlet create --from 0.0.0.0:15432 --to postgres
+ockam tcp-inlet create --from 0.0.0.0:15432 --via postgres
 
 EOS

examples/command/portals/databases/postgres/amazon_rds/aws_cli/analysis_corp/run_ockam.sh

@@ -34,6 +34,6 @@ ockam project enroll "$ENROLLMENT_TICKET"
 # This makes the remote postgres available on all localhost IPs at - 0.0.0.0:15432
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.postgres-outlet "true")'
-ockam tcp-inlet create --from 0.0.0.0:15432 --to postgres
+ockam tcp-inlet create --from 0.0.0.0:15432 --via postgres
 
 EOS

examples/command/portals/databases/postgres/docker/analysis_corp/run_ockam.sh

@@ -27,7 +27,7 @@ ockam project enroll "$ENROLLMENT_TICKET"
 # This makes the remote postgres available on all localhost IPs at - 0.0.0.0:15432
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.postgres-outlet "true")'
-until ockam tcp-inlet create --from 0.0.0.0:15432 --to postgres; do sleep 10; done
+ockam tcp-inlet create --from 0.0.0.0:15432 --via postgres
 
 # Run the container forever.
 tail -f /dev/null

examples/command/portals/databases/postgres/kubernetes/analysis_corp/run_ockam.sh

@@ -27,7 +27,7 @@ ockam project enroll /etc/ockam/enrollment/ticket
 # This makes the remote postgres available on localhost:15432
 ockam node create
 ockam policy create --resource tcp-inlet --expression '(= subject.postgres-outlet "true")'
-until ockam tcp-inlet create --from 0.0.0.0:15432 --to postgres; do sleep 10; done
+ockam tcp-inlet create --from 0.0.0.0:15432 --via postgres
 
 # Run the container forever.
 tail -f /dev/null

implementations/rust/ockam/ockam_command/src/tcp/outlet/static/create/after_long_help.txt

@@ -2,8 +2,8 @@
 # To create a new TCP Outlet to the TCP server, using the default node
 $ ockam tcp-outlet create --to 127.0.0.1:5000
 
-# To create a new TCP Outlet at the given address, to the TCP server, with given alias
-$ ockam tcp-outlet create --to 127.0.0.1:5000 --alias my-outlet --from payroll-db-outlet
+# To create a new TCP Outlet at the given address, to the TCP server
+$ ockam tcp-outlet create --to 127.0.0.1:5000 --from payroll-db-outlet
 
 # To create a new TCP Outlet to the TCP server, using a specific node
 $ ockam tcp-outlet create --at n1 --to 127.0.0.1:5000