letsencrypt: fix TransIP global_key handling

home-assistant · Feb 26, 2025 · 10bf73d · 10bf73d
1 parent 1ca5f12
commit 10bf73d
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 2 deletions.
diff --git a/letsencrypt/CHANGELOG.md b/letsencrypt/CHANGELOG.md
@@ -1,5 +1,9 @@
 # Changelog
 
+## 5.4.1
+
+- Fix TransIP global_key handling
+
 ## 5.4.0
 
 - Add additional arguments to certbot (dry-run, test-cert, verbose)

diff --git a/letsencrypt/config.yaml b/letsencrypt/config.yaml
@@ -1,5 +1,5 @@
 ---
-version: 5.4.0
+version: 5.4.1
 breaking_versions: [5.3.0]
 slug: letsencrypt
 name: Let's Encrypt

diff --git a/letsencrypt/rootfs/etc/services.d/lets-encrypt/run b/letsencrypt/rootfs/etc/services.d/lets-encrypt/run
@@ -276,7 +276,7 @@ elif [ "${CHALLENGE}" == "dns" ] && [ "${DNS_PROVIDER}" == "dns-transip" ]; then
     bashio::config.require 'dns.transip_username'
     bashio::config.require 'dns.transip_api_key'
     if bashio::config.has_value 'dns.transip_global_key'; then
-    "dns_transip_global_key=$(bashio::config 'dns.transip_global_key')"
+    echo "dns_transip_global_key = $(bashio::config 'dns.transip_global_key')" >> "/data/dnsapikey"
     fi
     if (( PROPAGATION_SECONDS < 240 )); then
         bashio::log.info "Increasing DNS propagation limit for TransIP to at least 240 seconds."