Echo

This passes the inputs it receives as outputs. It is convenient for cases where resources are managed outside Humanitec but still need to be consumed by workloads.

The Driver is a “Universal Driver” which means it can be used for all resource types.

Inputs #

The input schema should match the Resource outputs of the type that is being used with it.

The context placeholders can be used in the inputs which can be useful for generating fields that are matched to a particular Environment ID.

For example, a namespace could be defined as ${context.env.id}-internal

Outputs #

The outputs will match the inputs.

Examples #

See the Echo Driver examples page for a collection of examples.

This particular example shows how to allow a PostgreSQL database that is managed outside Humanitec to be consumed by a workload.

postgres-secretstore.yaml (view on GitHub) :

apiVersion: entity.humanitec.io/v1b1
kind: Definition
metadata:
  id: postgres-echo
entity:
  name: postgres-echo
  type: postgres
  driver_type: humanitec/echo
  driver_inputs:
    values:
      name: my-database
      host: products.postgres.dev.example.com
      port: 5432
    secret_refs:
      username:
        store: my-gsm
        ref: cloudsql-username
      password:
        store: my-gsm
        ref: cloudsql-password
  criteria:
    - {}