A deployment matches nothing

What it means#

A running deployment’s routes refer to a channel, a file transfer or an entity type that its project doesn’t have in the environment, for example after the channel was deleted or renamed. The running copies keep the addresses they started with, but the next start fails.

What raises it#

The problem is computed whenever the list is read, with one row for each missing name, whether the route reads it, publishes to it or stores into it. An API deployment whose webhook publishes to a channel that doesn’t exist raises it too. A name that a route builds in an expression or that comes from a project’s kamelet isn’t recorded with the version, so it raises nothing here and fails at the start instead.

What to check#

List the problems with their details, which name what is missing:

$ weikio problems --env <environment>

List the project’s channels:

$ weikio get channels --project <project>

List the environment’s entity types:

$ weikio get entity-store-policies --env <environment>

How to fix it#

Create what the route refers to, or publish a version of the integration that refers to a name that exists:

$ weikio channel create <project>/<channel>
$ weikio entitystore policy set <project>/<type> --env <environment>