Skip to content
Recued
Menu
← Back to recipes

Create a Heroku domain intake

by recued-core v1

Approval-gated Heroku domain creation workflow. It reads the app and existing domains, then creates exactly one custom domain through recued-core.heroku.domain.create using the documented hostname and sni_endpoint body fields. It does not enable or disable ACM, mutate SNI endpoints, delete domains, create log drains, change DNS, mutate config vars, or call arbitrary Heroku 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_hostname compare
Check if hostname key has data
app ?
domains_before_raw ?
created_domain ?
skip: step.has_hostname not_equal true
domains_after_raw ?
domains_after default
Apply default
domain_rows slice
Take a subset of
domain_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 4 configurable

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

heroku setting =
app name setting =
hostname setting =
sni endpoint setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Heroku connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

heroku herokudomaindnsacmapprovalpack:heroku

Details

11 steps 4 configurable settings recipe_id: create-heroku-domain-intake