fix: update DNS token script to work with Docker Compose profiles

- Check if certbot/zabbix-agent are running before recreating them
- Use profile-specific commands to recreate services with new AUTH_KEY
- Replace restart with up -d to ensure env_file changes are picked up
- Only affect services that are actually running, preserving profile setup

Author: paskal

scripts/update-dns-token.sh

@@ -3,5 +3,13 @@ set -e -u
 
 # write down new token
 sed -i "s/.*\AUTH_KEY.*/\AUTH_KEY=$($HOME/yandex-cloud/bin/yc iam create-token)/" "./private/environment/dnsrobocert.env"
-# make certbot and zabbix-agent read new AUTH_KEY
-docker compose up -d
+# recreate services that use the AUTH_KEY only if they are running
+if docker compose ps -q certbot | grep -q .; then
+    echo "Recreating certbot to pick up new AUTH_KEY..."
+    docker compose --profile certs up -d certbot
+fi
+
+if docker compose ps -q zabbix-agent | grep -q .; then
+    echo "Recreating zabbix-agent to pick up new AUTH_KEY..."
+    docker compose --profile monitoring up -d zabbix-agent
+fi