FerryDocs

What Ferry ignores

Ferry ignores each key that it does not support. Most of the time, it gives a warning.

Edit on GitHub
The warnings of a dry run
"warnings": [
  "blueprint: ignoring unsupported key 'x-defaults'",
  "service 'queue': ignoring unsupported key 'region'",
  "key value 'sessions': ignoring unsupported key 'ipAllowList'"
]

Ferry supports a part of the render.yaml format. A key that Ferry does not support is never an error. Thus a render.yaml that you have applies as it is.

With a warning

WhereIgnored
Top levelEach key that is not envVarGroups, databases, services or projects. This includes the x- keys.
A serviceKeys that Ferry does not support, such as region, scaling, previews or preDeployCommand.
A service with an imageruntime and image.creds.
A service with rootDirdockerContext.
A cron jobnumInstances.
A Redis entryEach key that is not type, name, plan, memoryLimit or cpuLimit: ipAllowList, maxmemoryPolicy…
A databaseOther keys: region, ipAllowList, diskSizeGB…
An envVars entryKeys that only Render uses, such as previewValue.

The warning has this form: service 'api': ignoring unsupported key 'region'.

With no warning

WhereIgnored
diskname and sizeGB. Ferry accepts them.
A static siteplan. Static sites have no plans on Render.

See Warnings for each message.

On this page