Configure Humanitec to model an application workload with resource dependencies, inject dynamic resource outputs into environment variables, and deploy via the Score CLI
domain: developer.humanitec.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Write a score.yaml file that declares the workload's containers, the required resources (e.g., a postgres database and a redis cache) under the 'resources' key, and maps resource outputs to container environment variables
Register resource definitions in Humanitec for each resource type, mapping them to actual cloud resources (e.g., RDS for postgres) with the appropriate driver and matching criteria
Use 'score-humanitec delta --deploy' or the Humanitec CLI to push the Score workload definition to a Humanitec application and environment, creating a deployment delta
Trigger a deployment in Humanitec by applying the delta via the Humanitec API or the humctl CLI, which resolves resource dependencies and injects dynamic values (connection strings, credentials) at deploy time
Verify the deployed workload by inspecting the running container environment variables in Humanitec's UI or via 'humctl get deployment-set' to confirm dynamic values are correctly injected
Known gotchas
Score resource references use a '${resources.<name>.<output>}' placeholder syntax; incorrect output names result in the placeholder being injected literally as a string rather than the resolved value
Humanitec resource matching uses criteria like app, env, and resource type; a resource definition with overly broad matching criteria can be selected unintentionally for a different environment, causing misconfiguration
The Score CLI and Humanitec platform are separate tools; 'score-humanitec' translates Score spec to Humanitec deployment deltas but does not itself perform the deploy — an explicit deploy step is always required
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?