nopermission.txt

# terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.

  + vsphere_folder.terraform
      datacenter:    "DC_DEMO"
      existing_path: "<computed>"
      path:          "terraform"


Plan: 1 to add, 0 to change, 0 to destroy.


# terraform apply
vsphere_folder.terraform: Creating...
  datacenter:    "" => "DC_DEMO"
  existing_path: "" => "<computed>"
  path:          "" => "terraform"
Error applying plan:

1 error(s) occurred:

* vsphere_folder.terraform: 1 error(s) occurred:

* vsphere_folder.terraform: error NoPermission

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.