v1.5.0

Push ARM images (#79)

* Update dependencies

* Use go 1.19

* Fix Dockerfile

* Test out circleci builds

* Revert circleci config changes

* Update version to 1.5.0

v1.4.0

Update version to 1.4.0 (#72)

* Update version to 1.4.0

* Update versions

* Remove comment from go.mod

* Revert "Update versions"

This reverts commit 3608497fbd834ff915ae5c368d4bd7d4db7b5bc8.

* Update versions

v1.3.2-2

Update dependencies and go version (#66)

* Update dependencies

* Use newer circleci images

* Fix dirs

* Update version

v1.3.2

Update dependencies and go version (#66)

* Update dependencies

* Use newer circleci images

* Fix dirs

* Update version

v1.3.1

Upgrade golang x crypto (#59)

v1.3.0

Support AWS MSK IAM (#57)

* Update modules

* Fill out MSK SASL support

* Fix lint errors

* Make config parsing strict

* Update README

* Remove unnecessary import

* Remove unnecessary log message

* Update config

* Fix config

* Update tests

* Update directories

* Update README

* Bump version

v1.2.0

Fix cluster config environment interaction (#55)

* Fix errors

* Fix version

* Don't check SASL mechanism if running from cluster config

* Update README

* Update README

* Fix README

* Fix README

* Update go version to 1.17

* Fix README

* Bump version

v1.1.1

Fix missing CertPath in TLSConfig in cluster.go (#49)

It looks like `CertPath` has been omitted from the TLS configuration when creating a broker connection.

When using client authentication with `topicctl bootstrap`, this is resulting in the following error:

```
./topicctl --cluster-config=kafka.yml bootstrap
...
ERROR local error: tls: unexpected message
```

v1.1.0

Support expanding cluster and topic yaml config files with the system…

v1.0.0

Support broker-API-only access to Kafka clusters as well as TLS and SASL authentication.