fix(support-chat): sync backend key from running bot
Deploy Canina / deploy (push) Successful in 21s
Deploy Canina / deploy (push) Successful in 21s
This commit is contained in:
1 parent
332d400a37
commit
31c55525c3
1 file changed
+12
@@ -66,6 +66,18 @@ fi
|
||||
|
||||
cd "$TARGET_DIR"
|
||||
|
||||
# Capture the bot key from Docker before recreating the bot; runner mounts may not include the host env file.
|
||||
if docker inspect canina-bot >/dev/null 2>&1; then
|
||||
LIVE_BOT_KEY=
|
||||
if [ -n "" ]; then
|
||||
grep -v ^SUPPORT_CHAT_KEY= .support-chat.env > .support-chat.env.tmp 2>/dev/null || true
|
||||
printf "SUPPORT_CHAT_KEY=%s\n" "" >> .support-chat.env.tmp
|
||||
mv .support-chat.env.tmp .support-chat.env
|
||||
chmod 600 .support-chat.env
|
||||
fi
|
||||
unset LIVE_BOT_KEY
|
||||
fi
|
||||
|
||||
# Inject support-chat runtime configuration from CI/CD without committing secrets.
|
||||
# The bot is the runtime owner of the internal key; synchronize only the
|
||||
# matching value into the colocated backend env file, never into Git or logs.
|
||||
|
||||
Reference in new issue
Block a user