eon-azcli-tool

Introduction

Dockerized client for Azure Bastion

Define "server" tunnels for IP and ports within .env file. See .env.sample for an example
Each environment variable name consists of {resource-tunnel-name}_{az-network-bastion-tunnel_arg_id}. The {resource-tunnel-name} is used for tunnel control so make it memorable
To make a connection to defined resources, run make from host. It then builds docker image and spawns a container for it.
Then to be able to control tunnels, connect to the container itself, via make cli
Then, from within the docker container run ./init. It should suffice to run it once for a given session (az login validity).
- The init script calls for login, then installs bastion extension and finally patches it for it to be able to be used from the outside.
Now you are all set and you can run the tunnel script: ./tunnel start {resource-tunnel-name} to start the tunnel (repeatedly for more resources) or ./tunnel stop {resource-tunnel-name} to stop it.
For now it is necessary to explicitly define ports to expose on host. There is an intention to make this automatic. Not ready yet though. Just set these in docker-compose.override.yml

~~Automatic port exposition to a host~~ Does not make much sense
Once bastion script is fixed, patching the library will no longer be necessary and can be dropped.