Approval-gated Heroku build creation workflow. It reads the app and recent builds, then creates exactly one build from a caller-supplied gzipped source blob URL through recued-core.heroku.build.create. It does not upload files itself, create apps, mutate config vars, roll back releases, stop or restart dynos, delete resources, or call arbitrary Heroku API routes.

How it works 13 steps

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

Process (13 steps)

■ app_key trim

Trim whitespace from setting app name

■ source_url trim

Trim whitespace from setting source blob url

■ source_version trim

Trim whitespace from setting source version

■ version_description trim

Trim whitespace from setting version description

■ has_source_url compare

Check if source url has data

■ app ?

■ builds_before_raw ?

■ created_build ?

skip: step.has_source_url not_equal true

■ builds_after_raw ?

■ builds_after default

Apply default

■ build_rows slice

Take a subset of

■ build_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

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

heroku setting =

app name setting =

buildpacks setting =

source version setting =

source blob url setting =

version description setting =