config.example.toml has no token_env placeholder under [chat.telegram] #882

Closed
opened 2026-10-27 13:38:08 +00:00 by sam · 0 comments
Owner

TelegramConfig.TokenEnv (internal/config/config.go:536) is a real, used field (cmd/archied/telegram_setup.go reads it via os.Getenv), but the commented [chat.telegram] block in config.example.toml only documents update_check_command / update_install_command -- there is no "# token_env = ..." line. An operator reading the example file to learn what's configurable would not discover this key exists.

Discovered while implementing archie-core-rs9 and testing tomlwrite.Apply against the real template: setting chat.telegram.token_env for the first time falls through to Apply's "key not found in table" path (uncomment header, append key), which works fine -- this is a documentation completeness gap in the template, not a functional blocker for archie-core-cbk.

Acceptance Criteria

Add a commented # token_env = "..." line (with a short comment on what it should point to, e.g. an env var containing the @BotFather token) under the commented [chat.telegram] block in config.example.toml, matching the style of the other commented-out optional fields.

Close reason

Added a commented token_env placeholder under [chat.telegram] in config.example.toml, matching the style of the other optional fields.


Imported from beads archie-core-1786637498998-349-fe936acb · GitHub #370 · type task · priority P2 · created 2026-08-08 · closed 2026-09-02

TelegramConfig.TokenEnv (internal/config/config.go:536) is a real, used field (cmd/archied/telegram_setup.go reads it via os.Getenv), but the commented [chat.telegram] block in config.example.toml only documents update_check_command / update_install_command -- there is no "# token_env = ..." line. An operator reading the example file to learn what's configurable would not discover this key exists. Discovered while implementing archie-core-rs9 and testing tomlwrite.Apply against the real template: setting chat.telegram.token_env for the first time falls through to Apply's "key not found in table" path (uncomment header, append key), which works fine -- this is a documentation completeness gap in the template, not a functional blocker for archie-core-cbk. ### Acceptance Criteria Add a commented `# token_env = "..."` line (with a short comment on what it should point to, e.g. an env var containing the @BotFather token) under the commented [chat.telegram] block in config.example.toml, matching the style of the other commented-out optional fields. ### Close reason Added a commented token_env placeholder under [chat.telegram] in config.example.toml, matching the style of the other optional fields. --- _Imported from beads `archie-core-1786637498998-349-fe936acb` · GitHub #370 · type task · priority P2 · created 2026-08-08 · closed 2026-09-02_
sam added the mediumtask labels 2026-10-27 13:38:08 +00:00
sam self-assigned this 2026-10-27 13:38:08 +00:00
sam closed this issue 2026-10-27 13:38:08 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#882