During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos mysql
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos mysql --help prints.
For more information see Chaos Engineering.
locally chaos mysql
Simulate MySQL (data plane) failure modes.
Simulate MySQL (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 mysql <fault> --percentage N locally chaos mysql <fault> reset locally chaos mysql show locally chaos mysql reset
Usage
locally chaos mysql [flags] locally chaos mysql [command]
Flags
-h, --help[=true|false] help for mysql
Subcommands
- locally chaos mysql 403 - Answer requests with 403, as when a role assignment has not replicated yet.
- locally chaos mysql 429 - Answer requests with 429 Too Many Requests and a retry hint.
- locally chaos mysql 500 - Answer requests with 500 Internal Server Error.
- locally chaos mysql disconnect - Close live connections cleanly, in the protocol's own terms, so the client has to reconnect.
- locally chaos mysql drop-connection - Close the connection without answering.
- locally chaos mysql failover - Fail the primary over on a schedule.
- locally chaos mysql latency - Hold requests for a random delay before they are handled.
- locally chaos mysql outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos mysql reset - Zero every MySQL (data plane) fault and drop every rule.
- locally chaos mysql restart - Restart the workload on a schedule.
- locally chaos mysql show - Print the current MySQL (data plane) chaos configuration.
- locally chaos mysql too-many-connections - Refuse new connections with the engine's own connection-limit error.
locally chaos mysql 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 MySQL (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 mysql 403 --percentage 25 locally chaos mysql 403 --percentage 100 --location london locally chaos mysql 403 reset --location london locally chaos mysql 403 --percentage 100 --name acct1
Usage
locally chaos mysql 403 [flags] locally chaos mysql 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 mysql 403 reset - Remove one 403 rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql 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 MySQL (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 mysql 429 --percentage 25 locally chaos mysql 429 --percentage 25 --retry-after 5s locally chaos mysql 429 --percentage 100 --location london locally chaos mysql 429 reset --location london locally chaos mysql 429 --percentage 100 --name acct1
Usage
locally chaos mysql 429 [flags] locally chaos mysql 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 mysql 429 reset - Remove one 429 rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql 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 MySQL (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 mysql 500 --percentage 25 locally chaos mysql 500 --percentage 100 --location london locally chaos mysql 500 reset --location london locally chaos mysql 500 --percentage 100 --name acct1
Usage
locally chaos mysql 500 [flags] locally chaos mysql 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 mysql 500 reset - Remove one 500 rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql 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 MySQL (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 mysql disconnect --percentage 25 --interval 10m locally chaos mysql disconnect --percentage 100 --interval 10m --location london locally chaos mysql disconnect reset --location london locally chaos mysql disconnect --percentage 100 --interval 10m --name acct1
Usage
locally chaos mysql disconnect [flags] locally chaos mysql 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 mysql disconnect reset - Remove one disconnect rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql 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 MySQL (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 mysql drop-connection --percentage 25 locally chaos mysql drop-connection --percentage 25 --interval 30s locally chaos mysql drop-connection --percentage 100 --location london locally chaos mysql drop-connection reset --location london locally chaos mysql drop-connection --percentage 100 --name acct1
Usage
locally chaos mysql drop-connection [flags] locally chaos mysql 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 mysql drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql failover
Fail the primary over on a schedule.
Fail the primary over on a schedule. On a hit the primary is unavailable for the rolled duration and any secondary serves reads only, then the primary returns. Without scope flags this sets the fault's rate on MySQL (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 mysql failover --percentage 25 --seconds 30-120 --interval 10m locally chaos mysql failover --percentage 100 --seconds 30-120 --interval 10m --location london locally chaos mysql failover reset --location london locally chaos mysql failover --percentage 100 --seconds 30-120 --interval 10m --name acct1
Usage
locally chaos mysql failover [flags] locally chaos mysql failover [command]
Flags
-h, --help[=true|false] help for failover
--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 mysql failover reset - Remove one failover rule, or put the whole fault back to zero.
locally chaos mysql failover reset
Remove one failover rule, or put the whole fault back to zero.
Reset the failover 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 mysql failover 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 mysql 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 MySQL (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 mysql latency --percentage 25 --seconds 30 locally chaos mysql latency --percentage 25 --seconds 30 --interval 30s locally chaos mysql latency --percentage 100 --seconds 30 --location london locally chaos mysql latency reset --location london locally chaos mysql latency --percentage 100 --seconds 30 --name acct1
Usage
locally chaos mysql latency [flags] locally chaos mysql 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 mysql latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql 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 MySQL (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 mysql outage --percentage 25 locally chaos mysql outage --percentage 25 --retry-after 5s locally chaos mysql outage --percentage 100 --location london locally chaos mysql outage reset --location london locally chaos mysql outage --percentage 100 --name acct1
Usage
locally chaos mysql outage [flags] locally chaos mysql 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 mysql outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos mysql 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 mysql 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 mysql reset
Zero every MySQL (data plane) fault and drop every rule.
Zero every MySQL (data plane) fault and drop every rule. Examples: locally chaos mysql reset
Usage
locally chaos mysql reset [flags]
Flags
-h, --help[=true|false] help for reset
--subscription string Subscription UUID (defaults to the configured default)
locally chaos mysql restart
Restart the workload on a schedule.
Restart the workload on a schedule. Every interval each target is rolled for; on a hit it restarts the way its own restart action does, dropping its connections. Without scope flags this sets the fault's rate on MySQL (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 mysql restart --percentage 25 --interval 10m locally chaos mysql restart --percentage 100 --interval 10m --location london locally chaos mysql restart reset --location london locally chaos mysql restart --percentage 100 --interval 10m --name acct1
Usage
locally chaos mysql restart [flags] locally chaos mysql restart [command]
Flags
-h, --help[=true|false] help for restart
--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 mysql restart reset - Remove one restart rule, or put the whole fault back to zero.
locally chaos mysql restart reset
Remove one restart rule, or put the whole fault back to zero.
Reset the restart 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 mysql restart 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 mysql show
Print the current MySQL (data plane) chaos configuration.
Print the current MySQL (data plane) chaos configuration. Examples: locally chaos mysql show
Usage
locally chaos mysql show [flags]
Flags
-h, --help[=true|false] help for show
--subscription string Subscription UUID (defaults to the configured default)
locally chaos mysql too-many-connections
Refuse new connections with the engine's own connection-limit error.
Refuse new connections with the engine's own connection-limit error. Without scope flags this sets the fault's rate on MySQL (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 mysql too-many-connections --percentage 25 locally chaos mysql too-many-connections --percentage 25 --retry-after 5s locally chaos mysql too-many-connections --percentage 100 --location london locally chaos mysql too-many-connections reset --location london locally chaos mysql too-many-connections --percentage 100 --name acct1
Usage
locally chaos mysql too-many-connections [flags] locally chaos mysql too-many-connections [command]
Flags
-h, --help[=true|false] help for too-many-connections
--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 mysql too-many-connections reset - Remove one too-many-connections rule, or put the whole fault back to zero.
locally chaos mysql too-many-connections reset
Remove one too-many-connections rule, or put the whole fault back to zero.
Reset the too-many-connections 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 mysql too-many-connections 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