Resources (components)

CRUD for product-scoped components (storage, databases, actions, etc.) via encrypted sdk-proxy.

Requires a linked project (ductape link) with product_tag and env_slug.

ductape resources types
ductape resources storage list
ductape resources storage get --tag uploads
ductape resources storage create -f storage.json
ductape resources storage update --tag uploads -f patch.json
ductape resources storage delete --tag uploads
ductape resources databases connect -f '{"tag":"main"}'

Resource types

storage, databases, graph, vector, caches, jobs, feature, actions, notifications, message-brokers, sessions, secrets, quota, health, fallback

The CLI normalizes these aliases: feature/features, quota/quotas, fallback/fallbacks, and health/healthcheck/healthchecks. Generated commands should prefer the singular canonical names above.

Features and resilience resources

ductape resources feature list --product payment-processing --json
ductape resources feature get -t create-payment --product payment-processing --json

ductape resources quota list --product payment-processing --json
ductape resources quota get -t payment-quota --product payment-processing --json

ductape resources fallback list --product payment-processing --json
ductape resources fallback get -t charge-payment --product payment-processing --json

ductape resources health list --product payment-processing --json
ductape resources health get -t paystack-health --product payment-processing --json

Feature fetch routing uses the SDK's feature.fetch(featureTag, productTag) signature internally. Quotas, fallbacks, and healthchecks use fetch(productTag, componentTag). The CLI handles this difference; do not construct proxy module names or parameter arrays manually.

Create and update administrative resources with -f:

ductape resources quota create --product payment-processing -f ductape/quotas/payment-quota.json --json
ductape resources fallback update -t charge-payment --product payment-processing -f ductape/fallbacks/charge-payment.json --json
ductape resources health create --product payment-processing -f ductape/healthchecks/paystack-health.json --json

These commands manage catalogue definitions. Runtime Feature execution and quota/fallback/health operations use the SDK or authenticated execution surface.

For products and apps at the workspace level, use ductape products and ductape apps.

Verb mapping

CLI	Proxy method
create	create
list	list
get	fetch
update	update
delete	delete
connect	connect

Use -f for JSON body files, or omit -f in a terminal to get interactive prompts (enum fields use dropdowns). Pass --no-interactive to require -f.

Transport

One route: POST …/sdk-proxy/execute. The body specifies module + method + params, encrypted like the Workbench.