FerryDocs

The result of an apply

The API answers with a BlueprintResult. It has the actions, the deploys and the warnings.

Edit on GitHub
Response (dry run)
{
  "dry_run": true,
  "actions": [
    { "resource": "datastore", "name": "sessions", "action": "create", "changes": [] },
    { "resource": "service", "name": "queue", "action": "create", "changes": [] }
  ],
  "deploys": [],
  "warnings": [
    "blueprint: ignoring unsupported key 'x-defaults'",
    "service 'queue': runtime 'elixir' is not supported natively; using auto-detection (add a Dockerfile)",
    "service 'queue': ignoring unknown plan 'enterprise' (known plans: free, starter, standard, pro, pro plus, pro max, pro ultra); set memoryLimit / cpuLimit instead",
    "service 'queue': ignoring unsupported key 'region'",
    "key value 'sessions': ignoring unsupported key 'ipAllowList'"
  ]
}

The returns a BlueprintResult. The CLI prints it as text. To get the raw , run ferry --json blueprint apply.

The fields

FieldTypeDescription
dry_runbooleantrue for a dry run.
actionsBlueprintAction[]Each resource of the blueprint, in the order of the apply.
deploysDeploy[]The deploys and restarts that the apply put in the queue. Empty for a dry run.
warningsstring[]Ignored keys, unknown plans, variables that you must set, services with no source, side effects that failed.

The fields of an action

FieldValues
resourceservice, datastore or env_group
nameThe name of the resource
actioncreate, update or unchanged
changesFor an update: a list of texts for people, such as "memory_limit: 512 MiB → 2 GiB"

On this page