# Connection improvements

## `zli v. 6.27.4`

### New

* **Connection failover.** With this `zli` release, connections to targets can failover safely in the event of an outage in a particular AWS region. If an outage should occur, you should not experience any disruption to your connections. <mark style="color:purple;">**In order to take advantage of this new capability, you must be running a minimum of**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`zli v. 6.27.0`**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**and**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`bzero v. 8.0.0`**</mark>

### Enhancements

* **Microsoft SQL Server.** Connecting to a SQL Server target with the Windows `zli` will open SQL Server Management Studio if installed
* **Windows RDP.** Connecting to an RDP target with the Windows `zli` will launch the Remote Desktop Connection application (`mstsc`) unless the `noAppStart` flag is specified
* **Color theme.** To support Powershell users, the `zli`'s font colors have been modified to be friendly to all users regardless of which OS they are running

### Fixes

* **Invalid and incorrect commands.** Resolved issue with invalid and incorrect commands not returning any message; now returns an error message and in cases where no arguments are provided, the `help` menu
* **Connect to RDP targets on Windows `zli`.** Resolved issue when running the `zli`  on Powershell that prevented the user from seeing the port number to connect to an RDP target (due to the color of the message the `zli` printed)
* **Debug daemon issues.** Kubernetes, DB, and web daemons can be started in the foreground with the `--debug` flag, which allows additional information to be surfaced for more accurate troubleshooting
* **Web daemon and query parameters.** Resolved an issue with the web daemon when handling query parameters

## `bzero v. 8.0.3`

### New

* **Connection failover.** With this `bzero` release, connections to targets can failover safely in the event of an outage in a particular AWS region. If an outage should occur, you should not experience any disruption to your connections. <mark style="color:purple;">**In order to take advantage of this new capability, you must be running a minimum of**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`zli v. 6.27.0`**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**and**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`bzero v. 8.0.0`**</mark>

### Enhancements

* **`send-logs` for Kubernetes agents.** `bzero v. 8.0.3` enables `zli send-logs` to send both the previous and current container logs to assist in troubleshooting for Kubernetes agents

### Fixes

* **`nodeSelector` in Helm chart.** Resolved inability to use `nodeSelector` as a value in the Helm chart due to spacing error. As a reminder, Helm does *not* automatically update the Helm chart when there are changes. To consume this fix, run `helm repo update bastionzero` to update to the latest chart version.
* **\[Released 19 July 2023] RBAC and port forwarding.** Resolved an issue seen in clusters that caused the agent to crash due to a user attempting to start a port forwarding session to a pod but only having `get` and not `create` RBAC permissions

## Web app & backend

### New

* **Connection failover.** This backend release contains the changes necessary to support connection failover. <mark style="color:purple;">**In order to take advantage of this new capability, you must be running a minimum of**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`zli v. 6.27.0`**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**and**</mark><mark style="color:purple;">**&#x20;**</mark><mark style="color:purple;">**`bzero v. 8.0.0`**</mark>

### Enhancements

* **Targets API.** Improved the [targets API](https://cloud.bastionzero.com/api/#get-/api/v2/targets) so all targets coming from Target Connect policies are based on what the associated agent type supports. `ConnectionState` can be used to query for targets by a specific connection state; if no parameter is provided, defaults to `ConnectionState.Open`
* **`send-logs` for Kubernetes agents.** This backend release contains the changes necessary to support `zli send-logs` for Kubernetes agents including previous and current container logs

### Fixes

* **Agent healthcheck.** Resolved an issue where an agent can be in contact with a connection node but still be marked as `offline`
* **Target status error message.** When trying to connect to a target by `target-name`, `target-name.environment`, or `target-name.environment-id` that is `offline`, BastionZero now returns an error message that a target by that name was found but is unable to be connected to because it is `offline`
* **Powershell autodiscovery script.** Resolved a typo in the Powershell autodiscovery script

For questions or to provide feedback on how we can improve our updates, reach out to [<mark style="color:purple;">product@bastionzero.com</mark>](mailto:product@bastionzero.com).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changes.bastionzero.com/2023/connection-improvements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.