Skip to content

refactor: call fn-letsencrypt-enable from auto-renew#408

Merged
josegonzalez merged 1 commit into
masterfrom
disable-direct-dokku-calls
May 12, 2026
Merged

refactor: call fn-letsencrypt-enable from auto-renew#408
josegonzalez merged 1 commit into
masterfrom
disable-direct-dokku-calls

Conversation

@josegonzalez

Copy link
Copy Markdown
Member

Replaces the two dokku letsencrypt:enable sub-process invocations inside cmd-letsencrypt-auto-renew with direct calls to fn-letsencrypt-enable. The batch path runs in a sub-shell so a single app's dokku_log_fail no longer aborts the whole renewal sweep.

The three remaining dokku certs:add / dokku certs:remove call sites in internal-functions cannot be converted today because the certs plugin in dokku core does not expose sourceable functions or plugin triggers for those operations; tracked upstream in dokku/dokku#8623. The cron-job script and cron-entries trigger keep invoking dokku letsencrypt:auto-renew because cron runs them in a fresh shell that needs the CLI wrapper to bootstrap the plugin env.

Replaces the two `dokku letsencrypt:enable` sub-process invocations inside `cmd-letsencrypt-auto-renew` with direct calls to `fn-letsencrypt-enable`. The batch path runs in a sub-shell so a single app's `dokku_log_fail` no longer aborts the whole renewal sweep.
@josegonzalez josegonzalez merged commit c4a2978 into master May 12, 2026
2 checks passed
@josegonzalez josegonzalez deleted the disable-direct-dokku-calls branch May 12, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant