# CloudBees Node: DynamicApi.evaluate needs no static container

## TL;DR

If your Node service needs flags that are not known at startup, use the dynamic API instead of redeploying with a new container. DynamicApi.evaluate takes a flag name and returns its value without a static container, and flags evaluated this way are sent to the CloudBees UI so you can manage them there. For ad-hoc properties, set a dynamicPropertyRuleHandler to compute values for property names the container never declared.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

Tool: Node. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Keep the evaluation context consistent: the same context fields must be present at evaluation time or dynamic rules misfire.

Context: Official docs (CloudBees, Node.js API): documents the dynamic API escape hatch: DynamicApi.evaluate works without a static container, and dynamicPropertyRuleHandler lets you evaluate properties the container never declared.
