Terraform workspace new

terraform workspace new my_new_workspace
Created and switched to workspace "my_new_workspace"!

You're now on a new, empty workspace. Workspaces isolate their state,
so if you run "terraform plan" Terraform will not see any existing state
for this configuration.

terraform workspace new
Expected a single argument: NAME.

Usage: terraform [global options] workspace new [OPTIONS] NAME

  Create a new Terraform workspace.

Options:

    -lock=false         Don't hold a state lock during the operation. This is
                        dangerous if others might concurrently run commands
                        against the same workspace. 
 
    -lock-timeout=0s    Duration to retry a state lock.

    -state=path         Copy an existing state file into the new workspace.

See also

• terraform [untaint | fmt | apply |show | state | init | plan | console | output | validate | destroy | debug | import | providers | get | graph | workspaces | resource | login | -var-file | state mv | state pull | state push | state replace-provider | state rm | force-unlock | env | tfe | --version | remote-exec | delete on termination | deprecated commands | terraform --help]
• Terraform, OpenTofu, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals: depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type, TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog, tfsec, tflint, Operators, Expressions: for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos