schema/TelegramNotificationRuleBase - property channel listed as required is not defined
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- openapi, yaml
- Domain
- api
Research direction
Start with TelegramNotificationRuleBase.yml and compare its required and properties sections, then read NotificationRuleBase.yml to check how endpointID is modeled. Verify the intended channel and connection fields against the referenced Flux telegram.message signature; done means the schema is internally consistent and the OpenAPI validation passes.
Written by the indexing model from the issue text.
Description
The property channel listed as required is not listed under property definitions.
TelegramNotificationRuleBase.yml
type: object
required: [type, messageTemplate, channel]
properties:
type:
description: The discriminator between other types of notification rules is "telegram".
type: string
enum: [telegram]
messageTemplate:
description: The message template as a flux interpolated string.
type: string
parseMode:
description: Parse mode of the message text per https://core.telegram.org/bots/api#formatting-options. Defaults to "MarkdownV2".
type: string
enum:
- MarkdownV2
- HTML
- Markdown
disableWebPagePreview:
description: Disables preview of web links in the sent messages when "true". Defaults to "false".
type: boolean
BTW: if the connection and sending of a notification is handled by the NotificationEndpoint defined as endpointID in NotificationRuleBase.yml, is it necessary to have the connection defining properties defined in the rule?
NOTE: In the flux documentation the telegram.message function signature includes a channel argument.
https://docs.influxdata.com/flux/v0.x/stdlib/contrib/sranka/telegram/message/
channel
text
token
?disableWebPagePreview
?parseMode
?silent
?url
Latest commit in openapi
commit ad64ba87e7dd666feb80bbb85d1757b3d290d6c3 (HEAD -> master, origin/master, origin/HEAD)
Author: wiedld <wiedld@users.noreply.github.com>
Date: Thu Sep 22 10:01:37 2022 -0700
Testing in K8SIDPE - latest commit
commit d3c2922e6c43cc6d7708a1622d6d2d7b1943b769 (HEAD -> master, origin/master, origin/HEAD)
Author: influx-acs[bot] <107396960+influx-acs[bot]@users.noreply.github.com>
Date: Tue Sep 27 01:45:24 2022 +0000
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from influxdata/openapi
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
influxdata/openapi#657 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
influxdata/openapi#653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
influxdata/openapi#240 ·
-
bug
influxdata/openapi#654 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
influxdata/openapi#636 ·
All issues in influxdata/openapi
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
astral-sh/python-build-standalone#1293 ·
-
package-update
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oSoWoSo/vOid_Community_repOsitory#185 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
carbon-language/carbon-lang#7821 ·