locally chaos control-plane

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

locally chaos control-plane

This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos control-plane --help prints.

For more information see Chaos Engineering and Control Plane API.

locally chaos control-plane

Simulate ARM (control plane) failure modes.

Simulate ARM (control plane) failure modes.

A fault command sets the fault's rate. With a scope flag (--plugin / --location)
it adds or edits a rule instead.

Examples:
locally chaos control-plane <fault> --percentage N
  locally chaos control-plane <fault> reset
  locally chaos control-plane show
  locally chaos control-plane reset

Usage

locally chaos control-plane [flags]
  locally chaos control-plane [command]

Flags

-h, --help[=true|false]   help for control-plane

Subcommands

locally chaos control-plane 403

Answer requests with 403, as when a role assignment has not replicated yet.

Answer requests with 403, as when a role assignment has not replicated yet. On
the control plane the error code is AuthorizationFailed; on a database the
engine's own equivalent error is sent instead.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane 403 --percentage 25
  locally chaos control-plane 403 --percentage 100 --location london
  locally chaos control-plane 403 reset --location london
  locally chaos control-plane 403 --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane 403 [flags]
  locally chaos control-plane 403 [command]

Flags

-h, --help[=true|false]     help for 403
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane 403 reset

Remove one 403 rule, or put the whole fault back to zero.

Reset the 403 fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane 403 reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane 429

Answer requests with 429 Too Many Requests and a retry hint.

Answer requests with 429 Too Many Requests and a retry hint. On a database the
engine's own throttling error is sent instead.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

--retry-after sets the Retry-After header the fault answers with, such as 5s.
Without one the service's usual hint is sent.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos control-plane 429 --percentage 25
  locally chaos control-plane 429 --percentage 25 --retry-after 5s
  locally chaos control-plane 429 --percentage 100 --location london
  locally chaos control-plane 429 reset --location london
  locally chaos control-plane 429 --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane 429 [flags]
  locally chaos control-plane 429 [command]

Flags

-h, --help[=true|false]     help for 429
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --retry-after string    Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane 429 reset

Remove one 429 rule, or put the whole fault back to zero.

Reset the 429 fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane 429 reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane 500

Answer requests with 500 Internal Server Error.

Answer requests with 500 Internal Server Error. On a database the engine's own
equivalent error is sent instead.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane 500 --percentage 25
  locally chaos control-plane 500 --percentage 100 --location london
  locally chaos control-plane 500 reset --location london
  locally chaos control-plane 500 --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane 500 [flags]
  locally chaos control-plane 500 [command]

Flags

-h, --help[=true|false]     help for 500
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane 500 reset

Remove one 500 rule, or put the whole fault back to zero.

Reset the 500 fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane 500 reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane drop-connection

Close the connection without answering.

Close the connection without answering. The client sees the connection reset,
with no status code or error body.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane drop-connection --percentage 25
  locally chaos control-plane drop-connection --percentage 100 --location london
  locally chaos control-plane drop-connection reset --location london
  locally chaos control-plane drop-connection --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane drop-connection [flags]
  locally chaos control-plane drop-connection [command]

Flags

-h, --help[=true|false]     help for drop-connection
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane drop-connection reset

Remove one drop-connection rule, or put the whole fault back to zero.

Reset the drop-connection fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane drop-connection reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane incident

Take each resource down for a while, then bring it back.

Take each resource down for a while, then bring it back. Every interval each
resource (or, on the directory and identity surfaces, the tenant) rolls against
the percentage; on a hit every request to it fails for the rolled duration,
answered as an outage would be, then it recovers on its own. Compare outage,
which fails requests for as long as it is armed.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

--seconds and --millis set the duration. A bare number is in the flag's unit;
one with its own suffix, such as 250ms or 1.5s, means what it says. One value N
picks 0 to N each time; MIN-MAX, such as 30-120, picks within that range. A
duration is required whenever the fault fires.

--interval is how often the fault starts, such as 10m. It is required whenever
the fault fires: nothing else sets it off.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos control-plane incident --percentage 25 --seconds 30-120 --interval 10m
  locally chaos control-plane incident --percentage 100 --seconds 30-120 --interval 10m --location london
  locally chaos control-plane incident reset --location london
  locally chaos control-plane incident --percentage 100 --seconds 30-120 --interval 10m --plugin Microsoft.Compute

Usage

locally chaos control-plane incident [flags]
  locally chaos control-plane incident [command]

Flags

-h, --help[=true|false]     help for incident
      --interval string       How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
      --location string       Scope this rule to one location, e.g. london
      --millis string         Duration in milliseconds, e.g. 250; N for 0 to N, or MIN-MAX for a range
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --seconds string        Duration in seconds, e.g. 30 or 1.5; N for 0 to N, or MIN-MAX for a range
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane incident reset

Remove one incident rule, or put the whole fault back to zero.

Reset the incident fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane incident reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane latency

Hold requests for a random delay before they are handled.

Hold requests for a random delay before they are handled. The response is
unchanged, just late.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

--seconds and --millis set the duration. A bare number is in the flag's unit;
one with its own suffix, such as 250ms or 1.5s, means what it says. The value is
a maximum: each firing picks 0 to N. A duration is required whenever the fault
fires.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos control-plane latency --percentage 25 --seconds 30
  locally chaos control-plane latency --percentage 100 --seconds 30 --location london
  locally chaos control-plane latency reset --location london
  locally chaos control-plane latency --percentage 100 --seconds 30 --plugin Microsoft.Compute

Usage

locally chaos control-plane latency [flags]
  locally chaos control-plane latency [command]

Flags

-h, --help[=true|false]     help for latency
      --location string       Scope this rule to one location, e.g. london
      --millis string         Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --seconds string        Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane latency reset

Remove one latency rule, or put the whole fault back to zero.

Reset the latency fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane latency reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane lro-delay

Slow long-running operations.

Slow long-running operations. The request is accepted as usual, and the
operation takes the extra time to complete.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

--seconds and --millis set the duration. A bare number is in the flag's unit;
one with its own suffix, such as 250ms or 1.5s, means what it says. The value is
a maximum: each firing picks 0 to N. A duration is required whenever the fault
fires.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos control-plane lro-delay --percentage 25 --seconds 30
  locally chaos control-plane lro-delay --percentage 100 --seconds 30 --location london
  locally chaos control-plane lro-delay reset --location london
  locally chaos control-plane lro-delay --percentage 100 --seconds 30 --plugin Microsoft.Compute

Usage

locally chaos control-plane lro-delay [flags]
  locally chaos control-plane lro-delay [command]

Flags

-h, --help[=true|false]     help for lro-delay
      --location string       Scope this rule to one location, e.g. london
      --millis string         Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --seconds string        Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane lro-delay reset

Remove one lro-delay rule, or put the whole fault back to zero.

Reset the lro-delay fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane lro-delay reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane lro-failure

Fail long-running operations.

Fail long-running operations. The request is accepted as usual, then the
operation ends in a terminal Failed provisioning state.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane lro-failure --percentage 25
  locally chaos control-plane lro-failure --percentage 100 --location london
  locally chaos control-plane lro-failure reset --location london
  locally chaos control-plane lro-failure --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane lro-failure [flags]
  locally chaos control-plane lro-failure [command]

Flags

-h, --help[=true|false]     help for lro-failure
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane lro-failure reset

Remove one lro-failure rule, or put the whole fault back to zero.

Reset the lro-failure fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane lro-failure reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane out-of-capacity

Fail resource creation, and updates that change a SKU or zone, with a capacity error such as AllocationFailed.

Fail resource creation, and updates that change a SKU or zone, with a capacity
error such as AllocationFailed.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane out-of-capacity --percentage 25
  locally chaos control-plane out-of-capacity --percentage 100 --location london
  locally chaos control-plane out-of-capacity reset --location london
  locally chaos control-plane out-of-capacity --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane out-of-capacity [flags]
  locally chaos control-plane out-of-capacity [command]

Flags

-h, --help[=true|false]     help for out-of-capacity
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane out-of-capacity reset

Remove one out-of-capacity rule, or put the whole fault back to zero.

Reset the out-of-capacity fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane out-of-capacity reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane outage

Fail requests for as long as the rule is armed, like a region or service that is down.

Fail requests for as long as the rule is armed, like a region or service that is
down. Each request rolls against the percentage, so at 100 every request fails
until the fault is turned off. Each service answers in its own terms, usually
503 Service Unavailable, and a protocol with live connections also closes the
ones open when the outage starts. For downtime that ends by itself, see
incident.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

--retry-after sets the Retry-After header the fault answers with, such as 5s.
Without one the service's usual hint is sent.

A value flag left out keeps what the row already has; a new rule starts with
none. 'reset' clears a row.

Examples:
locally chaos control-plane outage --percentage 25
  locally chaos control-plane outage --percentage 25 --retry-after 5s
  locally chaos control-plane outage --percentage 100 --location london
  locally chaos control-plane outage reset --location london
  locally chaos control-plane outage --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane outage [flags]
  locally chaos control-plane outage [command]

Flags

-h, --help[=true|false]     help for outage
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --retry-after string    Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane outage reset

Remove one outage rule, or put the whole fault back to zero.

Reset the outage fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane outage reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane quota-exceeded

Refuse requests because a quota is full.

Refuse requests because a quota is full. On the control plane a resource
creation (PUT) gets 409 Conflict with QuotaExceeded; on a data plane the
service's own quota error is sent, such as a full Service Bus queue.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane quota-exceeded --percentage 25
  locally chaos control-plane quota-exceeded --percentage 100 --location london
  locally chaos control-plane quota-exceeded reset --location london
  locally chaos control-plane quota-exceeded --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane quota-exceeded [flags]
  locally chaos control-plane quota-exceeded [command]

Flags

-h, --help[=true|false]     help for quota-exceeded
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane quota-exceeded reset

Remove one quota-exceeded rule, or put the whole fault back to zero.

Reset the quota-exceeded fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane quota-exceeded reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane recase-names

Change the casing of resource group names in responses, to find code that compares resource IDs case-sensitively.

Change the casing of resource group names in responses, to find code that
compares resource IDs case-sensitively.

Without scope flags this sets the fault's rate on ARM (control plane). With
--plugin / --location it adds or edits one rule, leaving the rate and other
rules alone.

A rule can be lower than the rate: "everywhere except one place" is a rate of
100 plus a rule at 0.

Examples:
locally chaos control-plane recase-names --percentage 25
  locally chaos control-plane recase-names --percentage 100 --location london
  locally chaos control-plane recase-names reset --location london
  locally chaos control-plane recase-names --percentage 100 --plugin Microsoft.Compute

Usage

locally chaos control-plane recase-names [flags]
  locally chaos control-plane recase-names [command]

Flags

-h, --help[=true|false]     help for recase-names
      --location string       Scope this rule to one location, e.g. london
      --percentage int        How often this fault fires, 0-100 (required)
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

Subcommands

locally chaos control-plane recase-names reset

Remove one recase-names rule, or put the whole fault back to zero.

Reset the recase-names fault.

With a scope flag, removes that rule so those requests use the fault's rate.
Without one, removes every rule and sets the rate to 0.

'reset --location X' removes the rule; '--percentage 0 --location X' keeps a
rule that never fires, which is how to say "everywhere except X".

Usage

locally chaos control-plane recase-names reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --location string       Scope this rule to one location, e.g. london
      --plugin string         Scope this rule to one ARM provider, e.g. Microsoft.Compute
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane reset

Zero every ARM (control plane) fault and drop every rule.

Zero every ARM (control plane) fault and drop every rule.

Examples:
locally chaos control-plane reset

Usage

locally chaos control-plane reset [flags]

Flags

-h, --help[=true|false]     help for reset
      --subscription string   Subscription UUID (defaults to the configured default)

locally chaos control-plane show

Print the current ARM (control plane) chaos configuration.

Print the current ARM (control plane) chaos configuration.

Examples:
locally chaos control-plane show

Usage

locally chaos control-plane show [flags]

Flags

-h, --help[=true|false]     help for show
      --subscription string   Subscription UUID (defaults to the configured default)
Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

A local cloud for you and your AI agents.

Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.