connection.value_invalid: Connection's key holds a value it can't

Connection's key holds a value it can't.

Area 11, External services; not declinable; the next step is usually the agent's.

A credential is read from a secret setting, which code never sees:

example

application {    connections: {        couriers: {            package: AcmeCouriers.v1            domains: [shipping]            credential: config.couriers_api_key            environment: config.couriers_environment        }    }}

jadpo checkcheck failed: 1 error, 6 files

error couriers's credential must be a secret setting

--> app.jadpo:6:25

  |6 |             credential: config.couriers_api_key  |                         ^^^^^^^^^^^^^^^^^^^^^^^ `couriers_api_key` isn't secret

reason: A credential is read from the deployment's environment and never seen by code, so it is a secret: true setting, config.<name> (area 10, "Secrets").
next: Add secret: true to couriers_api_key in config.jadpo (agent)
rule: connection.value_invalid
help: https://jadpo.dev/docs/errors/connection.value_invalid

development: { sandbox: } names the package's own operations and resources:

example

application {    connections: {        couriers: {            package: AcmeCouriers.v1            domains: [shipping]            environment: config.couriers_environment            development: {                sandbox: [bookings.creat]            }        }    }}

jadpo checkcheck failed: 1 error, 12 files

error couriers's sandbox: lists bookings.creat, which AcmeCouriers.v1 doesn't have

--> app.jadpo:8:27

  |8 |                 sandbox: [bookings.creat]  |                           ^^^^^^^^^^^^^^ no such operation or resource

reason: sandbox: lets the package's public operations and resources through to its sandbox in jadpo dev; AcmeCouriers.v1 has bookings.create and bookings.
next: Use bookings.create instead of bookings.creat (agent)
rule: connection.value_invalid
help: https://jadpo.dev/docs/errors/connection.value_invalid

erasure: { key: } names the field of the person's record holding what the provider knows them by, so it is a field of a person: true entity, of the type the package's erasure: by: names. Each of these is this error, such as `pay`'s `erasure:` key `User.plan` isn't a `CustomerId` (Erasure at providers).

Related