You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Hono 2.0.0, the default northbound connectivity for the tenants is set to Kafka (as stated here). The Hono sandbox that Kanto's quickstart and how-to Python scripts work with is updated accordingly to the latest Hono version.
Currently, all Kanto's quickstart and how-to Python scripts are AMQP-based, thus, the tenants they use to communicate via must be explicitly configured to enable that communication. This is a short-term measure and in the future we might think about migrating the scripts to Kafka (if needed and/or specific use cases emerge).
The text was updated successfully, but these errors were encountered:
…ants
Added an explicit messaging configuration set to AMQP for the provisioned Hono tenants
that are to be used by the quickstart and how-to Kanto Python scripts.
Signed-off-by: Konstantina Gramatova <[email protected]>
Added an explicit messaging configuration set to AMQP for the provisioned Hono tenants
that are to be used by the quickstart and how-to Kanto Python scripts.
Signed-off-by: Konstantina Gramatova <[email protected]>
As of Hono 2.0.0, the default northbound connectivity for the tenants is set to Kafka (as stated here). The Hono sandbox that Kanto's quickstart and how-to Python scripts work with is updated accordingly to the latest Hono version.
Currently, all Kanto's quickstart and how-to Python scripts are AMQP-based, thus, the tenants they use to communicate via must be explicitly configured to enable that communication. This is a short-term measure and in the future we might think about migrating the scripts to Kafka (if needed and/or specific use cases emerge).
The text was updated successfully, but these errors were encountered: