Caused by: io.micronaut.context.exceptions.ConfigurationException: Could not resolve placeholder ${DATAPLANE_CLIENT_ID} @kapa.ai

This error is part of a known issue in Airbyte 1.6.x where the dataplane credentials (

DATAPLANE_CLIENT_ID

/

DATAPLANE_CLIENT_SECRET

) are expected but not properly present in the Kubernetes secret used by the workload components, leading to failures like: -

couldn't find key dataplane-client-id in Secret .../airbyte-auth-secrets

- and Micronaut failing with

Could not resolve placeholder ${DATAPLANE_CLIENT_ID}

. [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468); [1.6.x deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] From the issues: - The values are stored in the

dataplane_client_credentials

DB table and then written into the same Kubernetes secret that also holds auth values (e.g.,

airbyte-auth-secrets

). [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468)] - When users define their own

airbyte-auth-secrets

(for instance to control instance admin email/password), the bootloader and workload pods still expect

dataplane-client-id

and

dataplane-client-secret

keys in that same secret, and fail if they’re missing. [[1.6.x deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - Some users tried deleting rows from

dataplane

/

dataplane_client_credentials

or recreating secrets, but the workload launcher continued to fail in 1.6.x. [[1.6.x deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - One user reports that moving to 1.7.1 made things “work out of the box,” suggesting the problem is largely specific to 1.6.x chart/bootloader behavior. [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468)] Given the knowledge sources, there is no documented, reliable workaround for 1.6.x beyond: 1. Avoid custom auth secret definitions that omit

dataplane-client-id

/

dataplane-client-secret

, or 2. Upgrade to a newer version (e.g., 1.7.1+) where users report the issue no longer occurs. [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468)] The sources do not provide a step‑by‑step fix for regenerating or manually wiring

DATAPLANE_CLIENT_ID

in 1.6.x; they only show that: - The bootloader rewrites the auth secret and manages dataplane credentials internally. [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468)] - Attempts to manually fix DB rows or secrets did not consistently resolve the error. [[1.6.x deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] So, based on the available information: - The

ConfigurationException: Could not resolve placeholder ${DATAPLANE_CLIENT_ID}

is a symptom of the same dataplane‑credential/secret wiring bug in 1.6.x. - The most reliable path indicated by the knowledge sources is to upgrade to a later Airbyte version (e.g., 1.7.1) rather than trying to patch 1.6.x. [[1.6.0 chart issue](https://github.com/airbytehq/airbyte/issues/62468)] If you share your exact Airbyte version and whether you’re using

abctl

or the Helm chart with a custom auth secret, I can map your situation more precisely to what’s described in these issues.