Recued
Menu
← Back to recipes

LaunchDarkly flag change brief

by recued-core v1 8 views

Use “LaunchDarkly flag change brief” in Recued. It provides a read-only brief for one LaunchDarkly feature flag in one environment.

How it works 14 steps

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

Process (14 steps)
project_key trim
Trim whitespace from setting project key
environment_key trim
Trim whitespace from setting environment key
flag_key trim
Trim whitespace from setting flag key
project ?
environment ?
flag ?
status ?
audit_raw ?
audit_entries default
Apply default
audit_count count
Count items in audit entries
audit_rows slice
Take a subset of
summarize ?
audit_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 8 configurable

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

focus setting = Summarize this LaunchDarkly flag for a release owner: current environment posture, status, recent changes, likely risks, missing context, and the safest next action. Do not invent facts outside the LaunchDarkly data.
flag key setting =
row limit setting = 20
max length setting = 900
audit after setting = 0
project key setting =
launchdarkly setting =
environment key setting = production

Trust & control

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

Permissions it requires

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

About

Tags

launchdarkly launchdarklyfeature-flagsrelease-managementaudit-logai-summarypack:launchdarkly

Details

14 steps 8 configurable settings recipe_id: flag-change-brief-launchdarkly