Automatic clients configuration

[famarting]

Overview

In order to improve developer experience for users doing amqp based messaging apps using enmasse we could add a feature to inject into user's deployments the configuration details to connect to enmasse amqp endpoints. This feature will rely on a common configuration feature provided by rhea and Qpid proton python:

• Qpid proton python, link to docs
• rhea nodejs client, link to docs

This will get a seamless integration between enmasse and user's application where developers will only need to care about provisioning messaging resources in enmasse and code their apps to use their amqp addresses, there will be no need for developers to hassle with connection details like hosts, ports, certificates, usernames or passwords.

Design

This is the general idea of how this could work, enmasse will generate a json file that is stored in a configmap or secret and is injected into user’s deployments using a volume mount from the CM or secret. Then in user’s applications the amqp client used will automatically pick and understand that json file to connect and authenticate to enmasse amqp endpoint.

There are several important details that are still not resolved, like in which enmasse CR to put the configuration needed or how to deal with usernames and passwords...