Jido.Chat.Telegram.Ingress (Jido Chat Telegram v1.1.0)

Copy Markdown View Source

Telegram ingress configuration and webhook subscription helpers.

jido_messaging treats ingress subscription callbacks as optional adapter extensions. Telegram maps those callbacks to the bot webhook control plane. Polling ingress is host-supervised, so subscription provisioning is not applicable there.

Summary

Functions

Deletes the Telegram webhook subscription for a bridge.

Ensures the Telegram webhook subscription for a bridge.

Lists the active Telegram webhook subscription for a bridge.

Returns the effective ingress mode.

Normalizes ingress settings from adapter callback options.

Types

mode()

@type mode() :: :webhook | :polling | :invalid

subscription_list_result()

@type subscription_list_result() :: {:ok, [map()]} | {:error, term()}

subscription_result()

@type subscription_result() :: {:ok, map()} | {:error, term()}

Functions

delete_subscription(bridge_id, subscription_id, opts)

@spec delete_subscription(String.t(), String.t(), keyword()) :: subscription_result()

Deletes the Telegram webhook subscription for a bridge.

ensure_subscription(bridge_id, opts)

@spec ensure_subscription(
  String.t(),
  keyword()
) :: subscription_result()

Ensures the Telegram webhook subscription for a bridge.

list_subscriptions(bridge_id, opts)

@spec list_subscriptions(
  String.t(),
  keyword()
) :: subscription_list_result()

Lists the active Telegram webhook subscription for a bridge.

mode(ingress)

@spec mode(map()) :: mode()

Returns the effective ingress mode.

normalize_opts(opts)

@spec normalize_opts(keyword()) :: map()

Normalizes ingress settings from adapter callback options.