openclaw/nix-openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/nix-openclaw.git synced 2026-07-24 21:25:23 -04:00
Code Issues 31 Packages Projects Releases Wiki Activity

[PR #30] Fix config schema alignment with openclaw #48

New Issue
Open
opened 2026-02-15 17:04:42 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:04:42 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/nix-openclaw/pull/30
Author: @jack-work
Created: 1/30/2026
Status: 🔄 Open

Base: main ← Head: main

📝 Commits (1)

  • 160a7e1 fix: bundle all runtime assets (extensions, docs)

📊 Changes

1 file changed (+1 additions, -4 deletions)

View changed files

📝 nix/scripts/gateway-install.sh (+1 -4)

📄 Description

Summary

Three fixes to align nix-clawbot with the openclaw config schema:

  1. byProvider → byChannel: Queue config was using messages.queue.byProvider but openclaw expects messages.queue.byChannel

  2. telegram → channels.telegram: Telegram config was generated at root level but openclaw expects it under channels.telegram

  3. gateway.auth.tokenFile: Added new option to inject gateway auth token from a file at activation time, supporting proper secret management

Fixes

  • Fixes #33 — Module generates config keys rejected by OpenClaw 2026.1.29
  • Fixes #17 — Generated config contains invalid key: messages.queue.byProvider

Changes

  • Renamed byProvider to byChannel in option definitions and mkRoutingConfig
  • Updated mkTelegramConfig to generate channels.telegram instead of root-level telegram
  • Added gateway.auth.tokenFile option at both global and instance levels
  • Added moltbotGatewayAuth activation step to inject token from file

Test plan

  • Build home-manager config with changes
  • Verify generated JSON contains byChannel instead of byProvider
  • Verify generated JSON contains channels.telegram instead of root-level telegram
  • Verify gateway token is injected from file during activation

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/openclaw/nix-openclaw/pull/30 **Author:** [@jack-work](https://github.com/jack-work) **Created:** 1/30/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`160a7e1`](https://github.com/openclaw/nix-openclaw/commit/160a7e1c14f3df5262235b0931d516b16c0492f7) fix: bundle all runtime assets (extensions, docs) ### 📊 Changes **1 file changed** (+1 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `nix/scripts/gateway-install.sh` (+1 -4) </details> ### 📄 Description ## Summary Three fixes to align nix-clawbot with the openclaw config schema: 1. **byProvider → byChannel**: Queue config was using `messages.queue.byProvider` but openclaw expects `messages.queue.byChannel` 2. **telegram → channels.telegram**: Telegram config was generated at root level but openclaw expects it under `channels.telegram` 3. **gateway.auth.tokenFile**: Added new option to inject gateway auth token from a file at activation time, supporting proper secret management ## Fixes - Fixes #33 — Module generates config keys rejected by OpenClaw 2026.1.29 - Fixes #17 — Generated config contains invalid key: messages.queue.byProvider ## Changes - Renamed `byProvider` to `byChannel` in option definitions and `mkRoutingConfig` - Updated `mkTelegramConfig` to generate `channels.telegram` instead of root-level `telegram` - Added `gateway.auth.tokenFile` option at both global and instance levels - Added `moltbotGatewayAuth` activation step to inject token from file ## Test plan - [x] Build home-manager config with changes - [x] Verify generated JSON contains `byChannel` instead of `byProvider` - [x] Verify generated JSON contains `channels.telegram` instead of root-level `telegram` - [x] Verify gateway token is injected from file during activation 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:04:42 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
maintainer-roadmap
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/nix-openclaw#48
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?