`weaver fabric capacity`¶

Synopsis¶

weaver fabric capacity [-h] --resource-group RESOURCE_GROUP --capacity-name CAPACITY_NAME [--subscription-id SUBSCRIPTION_ID] [--non-interactive] {status,resume,suspend}

Positional arguments¶

{status,resume,suspend}: No description is provided by the parser.

Options¶

-h, --help: show this help message and exit
--resource-group RESOURCE_GROUP: No description is provided by the parser.
--capacity-name CAPACITY_NAME: No description is provided by the parser.
--subscription-id SUBSCRIPTION_ID: Azure subscription ID when more than one subscription is available.
--non-interactive: Do not read stdin, wait for a keypress or open browser sign-in. Missing authorisation or required input is an error.

Responsibility and selection¶

fabric capacity delegates capacity management to the Azure CLI. The positional action is one of:

status reads the capacity;
resume requests that a suspended capacity resume;
suspend requests that the capacity suspend.

--resource-group and --capacity-name identify the Azure resource. --subscription-id selects a subscription explicitly. If it is omitted, Weaver checks FABRIC_SUBSCRIPTION_ID before using the Azure CLI's subscription context.

Execution¶

The Azure CLI and its fabric capacity commands must be installed and authenticated. Weaver invokes the corresponding Azure operation and reads the returned state and SKU when present.

resume and suspend do not poll until the requested state is reached. A successful resume response that is not yet active is reported as starting.

Interaction¶

The command has no confirmation, --yes or dry-run option. resume and suspend act as soon as the Azure CLI accepts the request. --non-interactive disables Weaver's browser-sign-in fallback; it does not authenticate or authorise the Azure CLI invocation.

Output and exit behaviour¶

Output names the capacity and reports the returned state, followed by the SKU when Azure supplies one. After resume, Weaver prints a follow-up status instruction when the returned state is not yet active.

The command exits 0 when the Azure CLI operation succeeds, including when a state transition is still in progress. A missing Azure CLI, unsupported action, authentication or authorisation failure, missing resource, or other non-zero Azure CLI result produces a non-zero status. No stable machine-readable output schema is promised.

Examples¶

Read capacity state:

weaver fabric capacity status \
  --resource-group parcel-platform \
  --capacity-name parcel-development

Request a resume in a selected subscription:

weaver fabric capacity resume \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000 \
  --non-interactive

Control a Fabric capacity¶

Use weaver fabric capacity to inspect, resume or suspend the Azure resource that supplies Fabric capacity. These commands wrap the Azure CLI; they do not open a Weaver Session, inspect a workspace or read a catalogue.

Capacity changes affect every workload assigned to that resource, not only the Weaver command or workspace you intend to run.

Prerequisites¶

The Azure CLI with its fabric capacity commands installed.
An Azure CLI sign-in authorised to read and change the capacity.
The Azure resource group and capacity name.
An explicit subscription ID when the Azure CLI context does not identify the intended subscription unambiguously.

Pass --subscription-id on the command or set FABRIC_SUBSCRIPTION_ID. An explicit option takes precedence over the environment variable; otherwise Weaver uses the Azure CLI subscription context.

Inspect state before changing it¶

weaver fabric capacity status \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000

The result names the capacity and reports the state returned by Azure, plus the SKU when available. A successful command proves only that Azure accepted and answered this request. It does not test Fabric workspace access or Weaver project configuration.

Resume and confirm the transition¶

Request a resume:

weaver fabric capacity resume \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000

The command returns after Azure accepts the operation. It does not poll until the capacity becomes active. A zero exit status may therefore be followed by a starting state.

Poll deliberately with status until Azure reports Active before starting work that needs the capacity:

weaver fabric capacity status \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000

Then run the intended Weaver or notebook operation. Capacity state and workspace readiness are separate boundaries: an active capacity does not prove that the caller can access a workspace, that an Environment is published or that a Fabric item exists.

Suspend only after work has settled¶

Check the Fabric jobs and other operations sharing the capacity outside this command. When they have finished, request suspension:

weaver fabric capacity suspend \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000

Suspend also returns when Azure accepts the request rather than when the final state is reached. Run status again when your operating procedure requires confirmation.

The command has no confirmation prompt, --yes option or dry-run mode. resume and suspend act immediately when Azure accepts them. Do not place unconditional suspension after a --no-wait notebook submission: that submission returns before the notebook reaches a terminal result.

Run from unattended automation¶

Authenticate the Azure CLI before the job, then prevent Weaver's browser-sign-in fallback:

weaver fabric capacity resume \
  --resource-group parcel-platform \
  --capacity-name parcel-development \
  --subscription-id 00000000-0000-0000-0000-000000000000 \
  --non-interactive

--non-interactive does not authenticate or authorise the Azure CLI request. A missing CLI, expired sign-in, wrong subscription, insufficient Azure permission or missing resource makes the command fail.

A bounded automation sequence should:

resume the capacity;
poll status until it is active, with an external timeout;
run the workload and wait for its real terminal outcome;
check whether other workloads still require the capacity; and
suspend it, then confirm the state if required.

Weaver does not provide the polling loop or decide whether other workloads have finished. Keep those estate-wide decisions in the scheduler or operating procedure that knows the shared capacity.

See weaver fabric capacity for exact syntax, subscription selection and exit behaviour. Use Push and run a Fabric notebook for the adjacent notebook lifecycle.

weaver fabric capacity¶