During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos apimanagement
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos apimanagement --help prints.
For more information see Chaos Engineering and API Management Emulator.
locally chaos apimanagement
Simulate API Management (data plane) failure modes.
Simulate API Management (data plane) failure modes. A fault command sets the fault's rate. With a scope flag (--location / --name) it adds or edits a rule instead. Examples: locally chaos apimanagement <fault> --percentage N locally chaos apimanagement <fault> reset locally chaos apimanagement show locally chaos apimanagement reset
Usage
locally chaos apimanagement [flags] locally chaos apimanagement [command]
Flags
-h, --help[=true|false] help for apimanagement
Subcommands
- locally chaos apimanagement 403 - Answer requests with 403, as when a role assignment has not replicated yet.
- locally chaos apimanagement 429 - Answer requests with 429 Too Many Requests and a retry hint.
- locally chaos apimanagement 500 - Answer requests with 500 Internal Server Error.
- locally chaos apimanagement 502 - Answer requests with 502 Bad Gateway from the service's front end, as when it cannot reach the app behind it.
- locally chaos apimanagement 504 - Answer requests with 504 Gateway Timeout from the service's front end, as when the app behind it takes too long.
- locally chaos apimanagement disconnect - Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
- locally chaos apimanagement drop-connection - Close the connection without answering.
- locally chaos apimanagement incident - Take each resource down for a while, then bring it back.
- locally chaos apimanagement latency - Hold requests for a random delay before they are handled.
- locally chaos apimanagement outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos apimanagement partial-response - Send the status, headers and part of the body, then cut the connection.
- locally chaos apimanagement reset - Zero every API Management (data plane) fault and drop every rule.
- locally chaos apimanagement show - Print the current API Management (data plane) chaos configuration.
- locally chaos apimanagement slow-body - Slow the response body down.
locally chaos apimanagement 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 API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos apimanagement 403 --percentage 25 locally chaos apimanagement 403 --percentage 100 --location london locally chaos apimanagement 403 reset --location london locally chaos apimanagement 403 --percentage 100 --name acct1
Usage
locally chaos apimanagement 403 [flags] locally chaos apimanagement 403 [command]
Flags
-h, --help[=true|false] help for 403
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement 403 reset - Remove one 403 rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement 403 reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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 API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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 apimanagement 429 --percentage 25 locally chaos apimanagement 429 --percentage 25 --retry-after 5s locally chaos apimanagement 429 --percentage 100 --location london locally chaos apimanagement 429 reset --location london locally chaos apimanagement 429 --percentage 100 --name acct1
Usage
locally chaos apimanagement 429 [flags] locally chaos apimanagement 429 [command]
Flags
-h, --help[=true|false] help for 429
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--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 apimanagement 429 reset - Remove one 429 rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement 429 reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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 API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos apimanagement 500 --percentage 25 locally chaos apimanagement 500 --percentage 100 --location london locally chaos apimanagement 500 reset --location london locally chaos apimanagement 500 --percentage 100 --name acct1
Usage
locally chaos apimanagement 500 [flags] locally chaos apimanagement 500 [command]
Flags
-h, --help[=true|false] help for 500
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement 500 reset - Remove one 500 rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement 500 reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 502
Answer requests with 502 Bad Gateway from the service's front end, as when it cannot reach the app behind it.
Answer requests with 502 Bad Gateway from the service's front end, as when it cannot reach the app behind it. The app never sees the request. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos apimanagement 502 --percentage 25 locally chaos apimanagement 502 --percentage 100 --location london locally chaos apimanagement 502 reset --location london locally chaos apimanagement 502 --percentage 100 --name acct1
Usage
locally chaos apimanagement 502 [flags] locally chaos apimanagement 502 [command]
Flags
-h, --help[=true|false] help for 502
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement 502 reset - Remove one 502 rule, or put the whole fault back to zero.
locally chaos apimanagement 502 reset
Remove one 502 rule, or put the whole fault back to zero.
Reset the 502 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 apimanagement 502 reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 504
Answer requests with 504 Gateway Timeout from the service's front end, as when the app behind it takes too long.
Answer requests with 504 Gateway Timeout from the service's front end, as when the app behind it takes too long. The app never sees the request. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos apimanagement 504 --percentage 25 locally chaos apimanagement 504 --percentage 100 --location london locally chaos apimanagement 504 reset --location london locally chaos apimanagement 504 --percentage 100 --name acct1
Usage
locally chaos apimanagement 504 [flags] locally chaos apimanagement 504 [command]
Flags
-h, --help[=true|false] help for 504
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement 504 reset - Remove one 504 rule, or put the whole fault back to zero.
locally chaos apimanagement 504 reset
Remove one 504 rule, or put the whole fault back to zero.
Reset the 504 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 apimanagement 504 reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement disconnect
Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
Close live connections cleanly, in the protocol's own terms, so the client has to reconnect. Every interval each open connection is rolled for. Compare drop-connection, which cuts them with nothing said. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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 apimanagement disconnect --percentage 25 --interval 10m locally chaos apimanagement disconnect --percentage 100 --interval 10m --location london locally chaos apimanagement disconnect reset --location london locally chaos apimanagement disconnect --percentage 100 --interval 10m --name acct1
Usage
locally chaos apimanagement disconnect [flags] locally chaos apimanagement disconnect [command]
Flags
-h, --help[=true|false] help for disconnect
--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
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement disconnect reset - Remove one disconnect rule, or put the whole fault back to zero.
locally chaos apimanagement disconnect reset
Remove one disconnect rule, or put the whole fault back to zero.
Reset the disconnect 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 apimanagement disconnect reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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. With --interval it also cuts live connections: every interval each is rolled for, and on a hit it is reset with nothing said - no close frame or goodbye. For a clean close, use disconnect. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos apimanagement drop-connection --percentage 25 locally chaos apimanagement drop-connection --percentage 25 --interval 30s locally chaos apimanagement drop-connection --percentage 100 --location london locally chaos apimanagement drop-connection reset --location london locally chaos apimanagement drop-connection --percentage 100 --name acct1
Usage
locally chaos apimanagement drop-connection [flags] locally chaos apimanagement drop-connection [command]
Flags
-h, --help[=true|false] help for drop-connection
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement drop-connection reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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 API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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 apimanagement incident --percentage 25 --seconds 30-120 --interval 10m locally chaos apimanagement incident --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos apimanagement incident reset --location london locally chaos apimanagement incident --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos apimanagement incident [flags] locally chaos apimanagement 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
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--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 apimanagement incident reset - Remove one incident rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement incident reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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. With --interval it also stalls live connections: every interval each is rolled for, and on a hit nothing crosses it in either direction until the rolled delay has passed. Nothing is dropped; it all arrives late. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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. --interval adds periodic action on live connections, such as every 30s, to the fault's per-request behaviour, which carries on as before. For periodic cuts with no per-request drops, arm disconnect instead. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos apimanagement latency --percentage 25 --seconds 30 locally chaos apimanagement latency --percentage 25 --seconds 30 --interval 30s locally chaos apimanagement latency --percentage 100 --seconds 30 --location london locally chaos apimanagement latency reset --location london locally chaos apimanagement latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos apimanagement latency [flags] locally chaos apimanagement latency [command]
Flags
-h, --help[=true|false] help for latency
--interval string Also act on live connections this often, e.g. 30s or 10m (adds to the per-request fault; use disconnect for periodic cuts only)
--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
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--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 apimanagement latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement latency reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement 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 API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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 apimanagement outage --percentage 25 locally chaos apimanagement outage --percentage 25 --retry-after 5s locally chaos apimanagement outage --percentage 100 --location london locally chaos apimanagement outage reset --location london locally chaos apimanagement outage --percentage 100 --name acct1
Usage
locally chaos apimanagement outage [flags] locally chaos apimanagement outage [command]
Flags
-h, --help[=true|false] help for outage
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--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 apimanagement outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos apimanagement 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 apimanagement outage reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement partial-response
Send the status, headers and part of the body, then cut the connection.
Send the status, headers and part of the body, then cut the connection. The client sees a response that ends early. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. Examples: locally chaos apimanagement partial-response --percentage 25 locally chaos apimanagement partial-response --percentage 100 --location london locally chaos apimanagement partial-response reset --location london locally chaos apimanagement partial-response --percentage 100 --name acct1
Usage
locally chaos apimanagement partial-response [flags] locally chaos apimanagement partial-response [command]
Flags
-h, --help[=true|false] help for partial-response
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--subscription string Subscription UUID (defaults to the configured default)
Subcommands
- locally chaos apimanagement partial-response reset - Remove one partial-response rule, or put the whole fault back to zero.
locally chaos apimanagement partial-response reset
Remove one partial-response rule, or put the whole fault back to zero.
Reset the partial-response 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 apimanagement partial-response reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement reset
Zero every API Management (data plane) fault and drop every rule.
Zero every API Management (data plane) fault and drop every rule. Examples: locally chaos apimanagement reset
Usage
locally chaos apimanagement reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement show
Print the current API Management (data plane) chaos configuration.
Print the current API Management (data plane) chaos configuration. Examples: locally chaos apimanagement show
Usage
locally chaos apimanagement show [flags]
Flags
-h, --help[=true|false] help for show
--subscription string Subscription UUID (defaults to the configured default)
locally chaos apimanagement slow-body
Slow the response body down.
Slow the response body down. The status and headers arrive as usual, then the body is written with a pause before every write. Without scope flags this sets the fault's rate on API Management (data plane). With --location / --name 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. --name acct1 matches that resource in any resource group; --name rg1/acct1 matches only rg1's. --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. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos apimanagement slow-body --percentage 25 --millis 100-800 locally chaos apimanagement slow-body --percentage 100 --millis 100-800 --location london locally chaos apimanagement slow-body reset --location london locally chaos apimanagement slow-body --percentage 100 --millis 100-800 --name acct1
Usage
locally chaos apimanagement slow-body [flags] locally chaos apimanagement slow-body [command]
Flags
-h, --help[=true|false] help for slow-body
--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
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--percentage int How often this fault fires, 0-100 (required)
--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 apimanagement slow-body reset - Remove one slow-body rule, or put the whole fault back to zero.
locally chaos apimanagement slow-body reset
Remove one slow-body rule, or put the whole fault back to zero.
Reset the slow-body 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 apimanagement slow-body reset [flags]
Flags
-h, --help[=true|false] help for reset
--location string Scope this rule to one location, e.g. london
--name string Scope this rule to one resource by name, e.g. acct1, or rg1/acct1 for one resource group's
--subscription string Subscription UUID (defaults to the configured default)
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in