Application Dependencies

Your application needs a database password, a cloud IAM permission, or an API
key, and you do not want any of those values sitting in your repository or in
your deployment configuration. The dependency block in your application
Component tells the platform to fetch them at deploy time and hand them to the
pod as environment variables or mounted secrets.

The block is available on the generic and language-specific application
Component types. Four engines are available.

Engine	What it does
`db`	Injects database connection details (user, password, host) as environment variables
`iam`	Binds cloud IAM roles to your application's Kubernetes service account
`ssm`	Pulls secrets from your cloud provider's Parameter Store or Secrets Manager
`onepassword`	Maps 1Password items into Kubernetes secrets

There is also a kafka dependency for injecting Kafka credentials — see
Access Management.

Inject Database Credentials

db

Attach a Cloud IAM Role

iam

Inject Secrets from Parameter Store

ssm

Inject Secrets from 1Password

onepassword

Related articles