idyl subnet - IDYL Docs

View and manage subnets. Subnets define groups of nodes organized by region. Admission is managed separately for developer accounts and provider fleets or nodes. Subnet runtime policy controls which workload isolation intent a subnet accepts. Use —allowed-isolation-class when creating or editing a subnet to allow container, secure-container, microvm, or a combination. Use —default-isolation-class when workloads that omit —isolation-class should inherit a subnet default. Runtime policy does not install or prove a runtime on provider nodes; scheduled workloads still require matching node capabilities. A globally unique slug is auto-generated when a subnet is created. An optional display name can be set for presentation; it is never used as an identifier.

Usage

idyl subnet

Aliases

subnets

Commands

Command	Description
`idyl subnet admission`	Manage subnet admission
`idyl subnet approve`	Approve a subnet for account deploy access
`idyl subnet attach`	Attach a leased fleet to a subnet
`idyl subnet create`	Create a subnet
`idyl subnet delete`	Delete a subnet
`idyl subnet edit`	Edit a subnet
`idyl subnet get`	Get managed subnet details or list managed subnets
`idyl subnet show`	Show current subnet details
`idyl subnet store-admission`	Admit Stores to a subnet
`idyl subnet unapprove`	Remove subnet deploy access from the account

Inherited flags

Flag	Description
`-a <string>, --account-id <string>`	Account ID to use, overriding the current context.
`-c <string>, --context <string>`	Use the named context for this command.
`--homedir <string>`	Override the configuration directory. Defaults to ~/.config/idyl.
`-n <string>, --namespace <string>`	Namespace to address, overriding the entered context.
`--network <string>`	Override the Network for this command.
`-p <string>, --profile <string>`	Override the access profile for this command.
`-s <string>, --subnet <string>`	Subnet to use for this command, overriding the current context.

Examples

# Create a subnet (slug auto-generated)
idyl subnet create --region us-east

# Create a subnet that accepts only secure-container isolation intent and defaults omitted isolation
idyl subnet create --region us-east --allowed-isolation-class secure-container --default-isolation-class secure-container

# Create a subnet that accepts only explicit secure-container isolation intent
idyl subnet create --region us-east --allowed-isolation-class secure-container

# Create a subnet that accepts only microVM isolation intent and defaults omitted isolation
idyl subnet create --region us-east --allowed-isolation-class microvm --default-isolation-class microvm

# Create a subnet with Registry Credentials and Vault enabled
idyl subnet create --region us-east --enable-registry-credentials --enable-vault

# Show current subnet details
idyl subnet show

# List subnets
idyl subnet list

# Get subnet details by slug
idyl subnet get <subnet-slug>

# Set developer admission mode
idyl subnet admission set --subnet <subnet-slug> --admission-type developer --mode approval

# Admit a developer account
idyl subnet admission grant --subnet <subnet-slug> --developer-account <account-id>

# Admit a provider fleet
idyl subnet admission grant --subnet <subnet-slug> --provider-fleet <fleet-id>

# Attach a fleet's capacity to a subnet
idyl subnet attach <subnet-slug> --fleet <fleet-id>

# Attach leased capacity to a subnet
idyl subnet attach <subnet-slug> --lease <lease-id>

# Delete a subnet
idyl subnet delete <subnet-slug>

Subcommand reference

`idyl subnet admission`

Manage typed subnet admission. Developer admission controls which accounts may submit workloads. Provider admission controls which fleets or nodes may join as capacity. A provider grant naming an account is an invitation: fleets that account creates in the subnet are admitted when they are created, and revoking the invitation revokes them. In approval mode, a fleet another account creates records a request the subnet’s owner decides with ‘idyl subnet admission request’.

Usage

idyl subnet admission

Aliases

admissions

Commands

Command	Description
`idyl subnet admission get`	Get subnet admission
`idyl subnet admission grant`	Grant subnet admission
`idyl subnet admission request`	Decide requests to join a subnet
`idyl subnet admission revoke`	Revoke subnet admission
`idyl subnet admission set`	Set an admission mode

Examples

idyl subnet admission get --subnet <subnet>
idyl subnet admission set --subnet <subnet> --admission-type provider --mode approval
idyl subnet admission grant --subnet <subnet> --developer-account <account-id>
idyl subnet admission grant --subnet <subnet> --provider-account <account-id>
idyl subnet admission grant --subnet <subnet> --provider-fleet <fleet-id>
idyl subnet admission grant --subnet <subnet> --provider-node <node-id>
idyl subnet admission revoke --subnet <subnet> --grant <grant-id>
idyl subnet admission request get --subnet <subnet>

`idyl subnet admission get`

Get subnet admission

Usage

idyl subnet admission get [flags]

Aliases

list
ls

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

`idyl subnet admission grant`

Grant subnet admission

Usage

idyl subnet admission grant [flags]

Flags

Flag	Description
`--developer-account <string>`	Account ID to grant developer admission.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.
`--provider-account <string>`	Account ID to invite: its fleets in the subnet are admitted when created.
`--provider-fleet <string>`	Fleet ID to grant provider admission.
`--provider-node <string>`	Node ID to grant provider admission.

`idyl subnet admission request`

List and decide the admission requests recorded on a subnet you own. A request is recorded when another account creates a fleet in a subnet whose provider admission mode is approval. Until it is decided, the fleet’s Attached condition reads AwaitingAdmissionApproval and the fleet serves nothing. Approving admits the fleet and creates its admission grant in the same step; rejecting leaves the fleet unadmitted.

Usage

idyl subnet admission request

Aliases

requests
req

Commands

Command	Description
`idyl subnet admission request approve`	Approve an admission request
`idyl subnet admission request get`	List admission requests
`idyl subnet admission request reject`	Reject an admission request

Examples

idyl subnet admission request get --subnet <subnet>
idyl subnet admission request approve <request-id> --subnet <subnet>
idyl subnet admission request reject <request-id> --subnet <subnet> --reason "capacity is full"

`idyl subnet admission request approve`

Approve a pending admission request, admitting its fleet or node to the subnet. The admission grant is created in the same step, and the fleet’s Attached condition turns true once the platform observes it.

Usage

idyl subnet admission request approve <request-id> [flags]

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.
`--reason <string>`	Note recorded with the decision, at most 1024 bytes.

Examples

idyl subnet admission request approve <request-id> --subnet <subnet>

`idyl subnet admission request get`

List every admission request recorded on a subnet you own, newest first.

Usage

idyl subnet admission request get [flags]

Aliases

list
ls

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

Examples

idyl subnet admission request get --subnet <subnet>
idyl subnet admission request get --subnet <subnet> -o json

`idyl subnet admission request reject`

Reject a pending admission request. No grant is created; the fleet stays created but serves nothing, and its Attached condition reads AdmissionRejected. A fleet never changes subnet, so it serves nothing until the subnet’s owner admits it with ‘idyl subnet admission grant’.

Usage

idyl subnet admission request reject <request-id> [flags]

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.
`--reason <string>`	Note recorded with the decision, at most 1024 bytes.

Examples

idyl subnet admission request reject <request-id> --subnet <subnet>
idyl subnet admission request reject <request-id> --subnet <subnet> --reason "capacity is full"

`idyl subnet admission revoke`

Revoke subnet admission

Usage

idyl subnet admission revoke [flags]

Flags

Flag	Description
`--grant <string>`	Required. Admission grant ID.

`idyl subnet admission set`

Set an admission mode

Usage

idyl subnet admission set [flags]

Flags

Flag	Description
`--admission-type <string>`	Required. Admission type: developer or provider.
`--mode <string>`	Required. Admission mode: open, approval, or invite.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

`idyl subnet approve`

Approve a subnet for account deploy access. This grants the current account permission to create new workloads in the subnet, provided the subnet’s region is also enabled for the account. Provider capacity admission is managed separately with ‘idyl subnet admission’.

Usage

idyl subnet approve <slug> [flags]

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

Examples

idyl subnet approve <subnet-slug>

`idyl subnet attach`

Attach a leased fleet to a subnet. A lease’s subnet is set once: a lease may be created without one and parks unattached, meters nothing, and holds no capacity until it is attached, after which cancelling the lease is the only detach. A fleet is not attached: it names its subnet when it is created, with ‘idyl fleet create —subnet’, and serves that subnet for its whole life.

Usage

idyl subnet attach <subnet-slug> [flags]

Flags

Flag	Description
`--lease <string>`	Required. Fleet lease to attach, by 12-digit lease ID.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

Examples

idyl subnet attach <subnet-slug> --lease <lease-id>

`idyl subnet create`

Create a new subnet in a region. A globally unique slug is auto-generated server-side. Use —display-name for optional presentation text; display names are not identifiers and need not be unique. Use runtime policy flags when the subnet should accept only specific workload isolation intent. If —default-isolation-class is set, workloads that omit —isolation-class inherit that default. If a runtime policy has no default, workloads must set —isolation-class explicitly. Runtime policy does not install or prove a runtime on provider nodes; scheduling still requires matching node capabilities. Registry Credentials and Vault have separate policies. Use —enable-registry-credentials for private image-pull credentials and —enable-vault for workload Secret and TLSCertificate projection. New subnets default to the denied root policy: workloads whose image would run as uid 0 are rejected at start. Pass —root-policy allowed to honor image users as-is.

Usage

idyl subnet create [flags]

Flags

Flag	Description
`--allow-daemonsets`	Admit DaemonSet workloads into the subnet, including those on the owner’s own nodes. Subnets with a runtime policy must opt in explicitly; a policy without it stops every DaemonSet’s pods.
`--allow-virtual-machines`	Admit VirtualMachine workloads into the subnet. Subnets with a runtime policy must opt in explicitly.
`--allowed-isolation-class <stringSlice>`	Allowed workload isolation intent for this subnet (container, secure-container, microvm); repeat the flag or comma-separate values.
`--daemonset-terms-account <stringSlice>`	Account whose DaemonSets may run on fleets other accounts own, by 12-digit account ID; repeat the flag or comma-separate values.
`--daemonset-terms-cpu <string>`	CPU those accounts’ DaemonSets may reserve together on one node of an accepting fleet (for example, 500m or 2).
`--daemonset-terms-gpus <uint64>`	GPUs those accounts’ DaemonSets may reserve together on one node of an accepting fleet. Default: `0`.
`--daemonset-terms-memory <string>`	Memory those accounts’ DaemonSets may reserve together on one node of an accepting fleet (for example, 512Mi or 4Gi).
`--default-isolation-class <string>`	Default isolation intent for workloads that omit —isolation-class; must be one of the allowed classes.
`--description <string>`	Subnet description.
`--disable-registry-credentials`	Disable RegistryCredential management, workload references, and image-pull release.
`--disable-vault`	Disable Vault management, workload references, and new assignment resolution.
`--display-name <string>`	Optional user-facing subnet display name.
`--enable-registry-credentials`	Enable RegistryCredential management, workload references, and image-pull release.
`--enable-vault`	Enable Vault management, workload references, and new assignment resolution.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.
`--region <string>`	Region to host the subnet in.
`--required-runtime-feature <stringSlice>`	Runtime feature required by this governed subnet; repeat the flag or comma-separate values (for example, example-feature-v1).
`--root-policy <string>`	Root policy for this subnet: allowed or denied. When denied, the subnet rejects workloads whose image would run as uid 0.

Examples

# Interactive — prompts for all required values
idyl subnet create

# Fully non-interactive
idyl subnet create --region us-east --display-name "Production"

# Create a subnet with Registry Credentials and Vault enabled
idyl subnet create --region us-east --enable-registry-credentials --enable-vault

# Create a subnet that allows root workloads
idyl subnet create --region us-east --root-policy allowed

# Create a subnet that accepts only secure-container isolation intent and defaults omitted isolation
idyl subnet create --region us-east --allowed-isolation-class secure-container --default-isolation-class secure-container

# Create a subnet that accepts only explicit secure-container isolation intent
idyl subnet create --region us-east --allowed-isolation-class secure-container

# Create a subnet that accepts only microVM isolation intent and defaults omitted isolation
idyl subnet create --region us-east --allowed-isolation-class microvm --default-isolation-class microvm

# Create a subnet that also admits VirtualMachine workloads
idyl subnet create --region us-east --allowed-isolation-class container --allow-virtual-machines

# Accept both container and secure-container isolation intent
idyl subnet create --region us-east --allowed-isolation-class container --allowed-isolation-class secure-container

# Let another account's DaemonSets use up to 500m CPU and 512Mi per node of accepting fleets
idyl subnet create --region us-east --daemonset-terms-account 550000000002 --daemonset-terms-cpu 500m --daemonset-terms-memory 512Mi

`idyl subnet delete`

Delete a subnet. The argument is the subnet’s canonical slug. You will be prompted for confirmation unless the —yes flag is provided.

Usage

idyl subnet delete <slug> [flags]

Flags

Flag	Description
`-y, --yes`	Skip confirmation prompts.

Examples

# Delete a subnet by slug (with confirmation)
idyl subnet delete <subnet-slug>

# Delete without confirmation
idyl subnet delete <subnet-slug> --yes

`idyl subnet edit`

Edit a subnet’s properties. The argument is the subnet’s canonical slug. Use —set-display-name to set presentation text or —clear-display-name to remove it. Display names are not identifiers and need not be unique. Runtime policy flags replace the subnet runtime policy. Use —allowed-isolation-class to set the allowed workload isolation intent. Use —default-isolation-class when workloads without explicit —isolation-class should inherit a subnet default. A runtime policy admits VirtualMachines and DaemonSets only with —allow-virtual-machines and —allow-daemonsets, so state them again on every replacement that should keep them; a policy without —allow-daemonsets stops the pods of every DaemonSet in the subnet. Use —clear-runtime-policy to remove subnet runtime policy. Runtime policy does not install or prove a runtime on provider nodes; scheduling still requires matching node capabilities. Use —root-policy to set the subnet’s root-user policy: denied rejects workloads whose image would run as uid 0 (with a reason-coded start failure on the node); allowed honors the image user as-is. The policy applies to assignments dispatched after the change; running pods keep running until their next restart or reschedule. DaemonSet terms flags replace the subnet’s terms whole: the accounts whose DaemonSets may run on fleets other accounts own, and what those DaemonSets may reserve together on one node (—daemonset-terms-cpu and —daemonset-terms-memory are required, —daemonset-terms-gpus defaults to 0). Narrower terms apply to every fleet at once and stop the pods they no longer admit; wider terms reach a fleet only when its owner accepts the new revision. —clear-daemonset-terms removes the terms and requires confirmation unless —yes is provided. Registry Credentials and Vault policy flags are independent. Disable operations require confirmation unless —yes is provided and do not destroy stored ciphertext.

Usage

idyl subnet edit <slug> [flags]

Flags

Flag	Description
`--allow-daemonsets`	Admit DaemonSet workloads into the subnet, including those on the owner’s own nodes. Subnets with a runtime policy must opt in explicitly; a policy without it stops every DaemonSet’s pods.
`--allow-virtual-machines`	Admit VirtualMachine workloads into the subnet. Subnets with a runtime policy must opt in explicitly.
`--allowed-isolation-class <stringSlice>`	Allowed workload isolation intent for this subnet (container, secure-container, microvm); repeat the flag or comma-separate values.
`--clear-daemonset-terms`	Remove the subnet’s DaemonSet terms, closing every fleet to other accounts’ DaemonSets at once.
`--clear-display-name`	Remove the subnet display name.
`--clear-runtime-policy`	Clear the subnet runtime policy so the subnet no longer filters by workload isolation intent.
`--daemonset-terms-account <stringSlice>`	Account whose DaemonSets may run on fleets other accounts own, by 12-digit account ID; repeat the flag or comma-separate values.
`--daemonset-terms-cpu <string>`	CPU those accounts’ DaemonSets may reserve together on one node of an accepting fleet (for example, 500m or 2).
`--daemonset-terms-gpus <uint64>`	GPUs those accounts’ DaemonSets may reserve together on one node of an accepting fleet. Default: `0`.
`--daemonset-terms-memory <string>`	Memory those accounts’ DaemonSets may reserve together on one node of an accepting fleet (for example, 512Mi or 4Gi).
`--default-isolation-class <string>`	Default isolation intent for workloads that omit —isolation-class; must be one of the allowed classes.
`--disable-registry-credentials`	Disable RegistryCredential management, workload references, and image-pull release.
`--disable-vault`	Disable Vault management, workload references, and new assignment resolution.
`--enable-registry-credentials`	Enable RegistryCredential management, workload references, and image-pull release.
`--enable-vault`	Enable Vault management, workload references, and new assignment resolution.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.
`--required-runtime-feature <stringSlice>`	Runtime feature required by this governed subnet; repeat the flag or comma-separate values (for example, example-feature-v1).
`--root-policy <string>`	Root policy for this subnet: allowed or denied. When denied, the subnet rejects workloads whose image would run as uid 0.
`--set-description <string>`	Set the subnet description.
`--set-display-name <string>`	Set the user-facing subnet display name.
`-y, --yes`	Skip confirmation prompts.

Examples

# Set a user-facing display name
idyl subnet edit <subnet-slug> --set-display-name "Production"

# Remove the display name
idyl subnet edit <subnet-slug> --clear-display-name

# Update subnet description
idyl subnet edit <subnet-slug> --set-description "New description"

# Enable Registry Credentials
idyl subnet edit <subnet-slug> --enable-registry-credentials

# Enable Vault
idyl subnet edit <subnet-slug> --enable-vault

# Disable Vault without an interactive prompt
idyl subnet edit <subnet-slug> --disable-vault --yes

# Accept only secure-container isolation intent and default omitted isolation
idyl subnet edit <subnet-slug> --allowed-isolation-class secure-container --default-isolation-class secure-container

# Accept only explicit secure-container isolation intent
idyl subnet edit <subnet-slug> --allowed-isolation-class secure-container

# Accept only microVM isolation intent and default omitted isolation
idyl subnet edit <subnet-slug> --allowed-isolation-class microvm --default-isolation-class microvm

# Accept both container and secure-container isolation intent
idyl subnet edit <subnet-slug> --allowed-isolation-class container --allowed-isolation-class secure-container

# Accept container isolation and keep admitting DaemonSets
idyl subnet edit <subnet-slug> --allowed-isolation-class container --allow-daemonsets

# Clear runtime policy
idyl subnet edit <subnet-slug> --clear-runtime-policy

# Allow root workloads on this subnet (a deliberate, recorded operator act)
idyl subnet edit <subnet-slug> --root-policy allowed

# Deny root workloads
idyl subnet edit <subnet-slug> --root-policy denied

# Let two accounts' DaemonSets reserve up to 1 CPU and 1Gi per node of accepting fleets
idyl subnet edit <subnet-slug> --daemonset-terms-account 550000000002,550000000003 --daemonset-terms-cpu 1 --daemonset-terms-memory 1Gi

# Remove the DaemonSet terms without an interactive prompt
idyl subnet edit <subnet-slug> --clear-daemonset-terms --yes

# Update typed admission policy
idyl subnet admission set --subnet <subnet-slug> --admission-type developer --mode approval

`idyl subnet get`

Get details of a specific managed subnet, or list managed subnets. With no arguments, lists subnets owned by the current account. With a slug argument, gets details of that managed subnet.

Usage

idyl subnet get [slug] [flags]

Aliases

list
ls

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

Examples

# List subnets
idyl subnet get

# Get subnet details by slug
idyl subnet get <subnet-slug>

# Get in JSON format
idyl subnet get <subnet-slug> -o json

`idyl subnet show`

Show details of the current subnet from the active context. The subnet is resolved from the —subnet flag, IDYL_SUBNET environment variable, or the current context.

Usage

idyl subnet show [flags]

Flags

Flag	Description
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

Examples

# Show current subnet details
idyl subnet show

# Show current subnet in JSON format
idyl subnet show -o json

`idyl subnet store-admission`

Admit Stores to a subnet, as its owner. Computers and Filesystems created in the subnet keep their saved versions in an admitted Store: the one they name, or the subnet’s default. Admission governs only new placement; existing Computers and Filesystems keep their Store and stay readable when it is removed. ‘idyl store get’ lists the admitted Stores.

Usage

idyl subnet store-admission

Aliases

store-admissions

Commands

Command	Description
`idyl subnet store-admission add`	Admit a Store to a subnet
`idyl subnet store-admission edit`	Change whether an admitted Store is the subnet default
`idyl subnet store-admission remove`	Stop admitting a Store to a subnet

Examples

idyl subnet store-admission add archive --subnet <subnet> --default
idyl subnet store-admission edit archive --subnet <subnet> --default=false
idyl subnet store-admission remove archive --subnet <subnet>

`idyl subnet store-admission add`

Admit a Store to the subnet named by —subnet. —default makes it the subnet’s only default Store; —default=false admits it without changing the default. Without —default the server keeps its own choice.

Usage

idyl subnet store-admission add <store> [flags]

Flags

Flag	Description
`--default`	Make this Store the subnet’s default.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

`idyl subnet store-admission edit`

Change whether an admitted Store is the default of the subnet named by —subnet. —default makes it the only default; —default=false withdraws it, leaving the subnet without a default rather than choosing another.

Usage

idyl subnet store-admission edit <store> [flags]

Flags

Flag	Description
`--default`	Required. Whether this Store is the subnet’s default.
`-o <string>, --output <string>`	Output format: table, json, yaml. Default: `table`.

`idyl subnet store-admission remove`

Stop new placement on a Store in the subnet named by —subnet. Computers and Filesystems already in the Store keep it and stay readable. Removing the default leaves the subnet without one.

Usage

idyl subnet store-admission remove <store>

`idyl subnet unapprove`

Remove subnet deploy access from the account. Existing workloads are not stopped, but new deployments to the subnet will be blocked once access is removed.

Usage

idyl subnet unapprove <slug> [flags]

Flags

Flag	Description
`-y, --yes`	Skip confirmation prompts.

Examples

idyl subnet unapprove <subnet-slug> --yes

​Usage

​Aliases

​Commands

​Inherited flags

​Examples

​Subcommand reference

​idyl subnet admission

​Usage

​Aliases

​Commands

​Examples

​idyl subnet admission get

​Usage

​Aliases

​Flags

​idyl subnet admission grant

​Usage

​Flags

​idyl subnet admission request

​Usage

​Aliases

​Commands

​Examples

​idyl subnet admission request approve

​Usage

​Flags

​Examples

​idyl subnet admission request get

​Usage

​Aliases

​Flags

​Examples

​idyl subnet admission request reject

​Usage

​Flags

​Examples

​idyl subnet admission revoke

​Usage

​Flags

​idyl subnet admission set

​Usage

​Flags

​idyl subnet approve

​Usage

​Flags

​Examples

​idyl subnet attach

​Usage

​Flags

​Examples

​idyl subnet create

​Usage

​Flags

​Examples

​idyl subnet delete

​Usage

​Flags

​Examples

​idyl subnet edit

​Usage

​Flags

​Examples

​idyl subnet get

​Usage

​Aliases

​Flags

​Examples

​idyl subnet show

​Usage

​Flags

​Examples

​idyl subnet store-admission

​Usage

​Aliases

​Commands

​Examples

​idyl subnet store-admission add

​Usage

​Flags

​idyl subnet store-admission edit

Usage

Aliases

Commands

Inherited flags

Examples

Subcommand reference

`idyl subnet admission`

Usage

Aliases

Commands

Examples

`idyl subnet admission get`

Usage

Aliases

Flags

`idyl subnet admission grant`

Usage

Flags

`idyl subnet admission request`

Usage

Aliases

Commands

Examples

`idyl subnet admission request approve`

Usage

Flags

Examples

`idyl subnet admission request get`

Usage

Aliases

Flags

Examples

`idyl subnet admission request reject`

Usage

Flags

Examples

`idyl subnet admission revoke`

Usage

Flags

`idyl subnet admission set`

Usage

Flags

`idyl subnet approve`

Usage

Flags

Examples

`idyl subnet attach`

Usage

Flags

Examples

`idyl subnet create`

Usage

Flags

Examples

`idyl subnet delete`

Usage

Flags

Examples

`idyl subnet edit`

Usage

Flags

Examples

`idyl subnet get`

Usage

Aliases

Flags

Examples

`idyl subnet show`

Usage

Flags

Examples

`idyl subnet store-admission`

Usage

Aliases

Commands

Examples

`idyl subnet store-admission add`

Usage

Flags

`idyl subnet store-admission edit`