Approval-gated Fly.io ACME certificate request workflow. It reads the target app and existing certificate summaries for context, validates the caller-supplied hostname, then requests exactly one ACME certificate through recued-core.flyio.certificate.request_acme. It does not upload custom certificates, remove certificates, mutate DNS, assign IPs, create machines, alter secrets, or call arbitrary Fly.io API routes.

How it works 11 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (11 steps)

■ app_key trim

Trim whitespace from setting app name

■ hostname_key trim

Trim whitespace from setting hostname

■ has_app_name compare

Check if app key has data

■ has_hostname compare

Check if hostname key has data

■ app ?

■ certificates_raw ?

■ skip_request any

Check if any of the conditions are true

■ requested_certificate ?

skip: step.skip_request equal true

■ existing_count count

Count items in certificates raw result

■ skipped compare

Check if skip request equals true

■ card to_summary

Format results as a summary card

Settings 3 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

flyio setting =

app name setting =

hostname setting =