Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lucasheld.uptime_kuma.notification Unsupported parameters telegramBotToken, telegramChatID, type #51

Open
wolfi1k opened this issue Jul 14, 2024 · 0 comments

Comments

@wolfi1k
Copy link

wolfi1k commented Jul 14, 2024

Hi,
i am trying to setup a notification using the lucasheld.uptime_kuma.notification module.

Ansible version: ansible [core 2.16.2]
Uptime Kuma Ansible-Galaxy version: lucasheld.uptime_kuma 1.2.0
uptime_kuma_api Version (pip): Version: 1.2.1

I am trying the following config adopting the example from the documentation:

- name: Add Telegram Notification
  lucasheld.uptime_kuma.notification:
    api_url: "{{ uptime_kuma_api_url }}"
    api_token: "{{ api_token }}"
    name: Telegram
    type: telegram
    isDefault: true
    applyExisting: true
    telegramBotToken: "{{ uptime_kuma_telegram_bot_token }}"
    telegramChatID: "{{ uptime_kuma_telegram_chat_id }}"
    state: present

However when i run this with Ansible i get the following error:

TASK [uptime-kuma : Add Telegram Notification] **************************************************************************************************************************************************
fatal: [XXX.XXX.X.XX]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (lucasheld.uptime_kuma.notification) module: telegramBotToken, telegramChatID, type. Supported parameters include: api_headers, api_password, api_ssl_verify, api_timeout, api_token, api_url, api_username, api_wait_events, applyExisting, id, isDefault, name, state (default)."}

It seems like the parameter is not implemented at all.
It is also only listed in the examples, but not in the documentation itself.
Is there an error in the example, my usage or are these commands simply not implemented?

Best Regards
Wolfi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant