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

Update alert_action.html.markdown #81

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

SpawW
Copy link

@SpawW SpawW commented Jan 15, 2024

Add information about unicity of channel_id for telegram

Add information about unicity of channel_id for telegram
@SpawW
Copy link
Author

SpawW commented Jan 15, 2024

Sample error when we try to use the same channel ID in 2 different alert actions

2│ Error: could not create an alert action with ID , error: Bad request: api respond with status code: 400, error code: ERROR, message: This 'channelId' is already set in another Telegram alert action, remove it first
3│
4│ with ilert_alert_action.aa_dev_telegram,
5│ on aa_dev_telegram.tf line 1, in resource "ilert_alert_action" "aa_dev_telegram":
6│ 1: resource "ilert_alert_action" "aa_dev_telegram" {
7│

@STLVRTX
Copy link
Collaborator

STLVRTX commented Feb 1, 2024

Hello, sorry for the late response, and thank you for the PR!

We're currently evaluating if we lift this restriction in our Telegram integration. When a decision was made I will provide an update comment on this PR. For now we can leave this open until a decision is made and then adjacently adjust the docs.

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

Successfully merging this pull request may close these issues.

2 participants