The Intersight provider is built directly from the OpenAPI-based Intersight REST API and its representation of the underlying data models. At the time of this writing, the Intersight provider does not provide high level resources such as a single resource representing a network interface or network adapter.
From my experience, at this point in time, I recommend approaching the provider as an easier to consume interface for the direct REST API calls. Or, put another way, it's a simplified means (using Terraform Hashicorp Language) to make REST API calls without the need to write a lot of Python REST overhead.
It is under active, rapid development so please provide feedback via the GitHub Issues page for the engineering team to have visibility with provider usage issue. Also, reference that page to investigate possible reasons for behaviors in this example repo differing from documented.
Since the provider essentially maps directly to the exact model representation present in the REST API, it's essential to understand the model at least with respect to the server profile.
You'll need to create an API key and secret key file within Intersight for the account into which you will be deploying these Terraform defined resources. You can generate those credentials here..
The entire process for setting up your authentication for this workshop is described in 01-rest/hands-on-exercise.md.
In addition to the authentication related environment variables you defined in the hands-on exercise (TF_VAR_apikey, TF_VAR_secretkey, TF_VAR_target_organization), you are strongly advised to also define some additional environment variables related to this Terraform example. Those variables can be found in the variables.tf file. The critical variable to set would be the dcnm user password:
export TF_VAR_dcnm_password='S0meTh!ngSecur3'Beyond those customizations, the standard Terraform operations apply at this point:
terraform init
terraform plan
terraform apply