IO

Since Envoy will always depend on libc, it seems reasonable for IO to also.

Use the Charm logger consistently through IO.

Use github.com/lestrrat-go/jwx/v3 for all JWT operations.

Keep third-party dependencies at a minimum.

No third-party SDKs are used by IO to call networked APIs.

Use SCP and SFTP to configure and observe IO.

Use SSH to make the IO TUI available to remote users.

Build Vault integration and use Vault to manage secrets.

All protobuf support code that IO uses is generated within the project.

Build support for AT Protocol Authorization directly into IO.

Build support for OAuth into IO.

Build Nomad integration and use Nomad to manage containers.

Configure IO with the Hashicorp Configuration Language.

Build support for the ACME protocol into IO to automatically provision SSL certificates.

Use SQLite for IO internal storage and general data persistence.

Use Bubble Tea to build a terminal user interface for IO.

Use “IO” to clearly assert the project’s goals.

Use Linux Abstract Sockets for local communication.

IO is an Envoy controller and Envoy is a core component of IO.