- Home
- Integration and extensions
- Drivers
- Generic Drivers
- Static
-
- Overview
-
- Overview
- Deploy your Application
- Manage your Java application
- Migrate an Application
- Provision Amazon S3 Buckets
- Deploy an Amazon S3 Resource to production
- Scaffold a new Workload and create staging and prod Environments
- Update Resource Definitions for related Applications
- Use existing Terraform modules
- Provision a Redis cluster on AWS using Terraform
- Perform daily developer activities (debug, rollback, diffs, logs)
- Deploy ephemeral Environments
-
-
Static
DEPRECATED
The humanitec/static
Driver has been renamed to humanitec/echo
. Please use the Echo Driver instead.
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.
Property | Description |
---|---|
Resource type | Any |
Account type | None |
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.
Example #
The humanitec/static
Driver to allow a MySQL database that is managed outside Humanitec to be consumed by a workload.
curl https://api.humanitec.io/orgs/${HUMANITEC_ORG}/resources/defs \
-H "Authorization: Bearer ${HUMANITEC_TOKEN}" \
-H "Content-Type: application/json" \
--data-binary '{
"id": "static-mysql",
"name": "Static MySQL",
"type": "mysql",
"driver_type": "humanitec/static",
"driver_inputs": {
"values": {
"name": "user_profiles",
"host": "products.mysql.prod.example.com",
"port": 3306
},
"secret": {
"username": "profile_robot",
"password": "5ecr3t-p455w0rd"
}
},
"criteria": [
{
"app_id": "products",
"env_id": "production"
}
]
}'