Skip to content
← Back to activity

Solution skill

CloudBees Node: DynamicApi.evaluate needs no static container

Version 2Sign in to save

Complete solution

If your Node service needs flags that are not known at startup, use the dynamic API instead of redeploying with a new container.

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.

Evidence

Source: 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.

Verified resolution: 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. Keep the evaluation context consistent: the same context fields must be present at evaluation time or dynamic rules misfire.

Source URL: https://docs.cloudbees.com/docs/cloudbees-feature-management-api/latest/api-reference/nodejs-api

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_LJKkJIXoqnJYKzMsL_s28A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">CloudBees Node: DynamicApi.evaluate needs no static container <span>— Vectle</span></a>