You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you provided a full/minimal configuration to reproduce the issue?
Have you [tested with the latest master] to confirm the issue still exists?
Have you provided the terraform console logs with environment variable set to TF_LOG=trace?
Description
When I run a plan I am finding that the resource intersight_resourcepool_qualification_policy is ignoring the additional_properties attributes for the following ObjectTypes:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:+ create
Terraform will perform the following actions:# intersight_resourcepool_qualification_policy.test will be created+resource"intersight_resourcepool_qualification_policy""test" {
+account_moid=(known after apply)
+ancestors=(known after apply)
+class_id="resourcepool.QualificationPolicy"+create_time=(known after apply)
+description="dummy"+domain_group_moid=(known after apply)
+id=(known after apply)
+mod_time=(known after apply)
+moid=(known after apply)
+name="dummy"+object_type="resourcepool.QualificationPolicy"+organization=(known after apply)
+owners=(known after apply)
+parent=(known after apply)
+permission_resources=(known after apply)
+qualifiers=[
+ {
+ additional_properties =jsonencode(
{
+ AdaptersRange = {
+ ConditionType ="RANGE"+ MaxValue =2+ MinValue =1+ ObjectType ="AdaptersRangeFilter"
}
}
)
+ class_id ="resource.NetworkAdaptorQualifier"+ object_type ="resource.NetworkAdaptorQualifier"
},
+ {
+ class_id ="resource.BladeQualifier"+ object_type ="resource.BladeQualifier"
},
+ {
+ additional_properties =jsonencode(
{
+ CPUCoresRange = {
+ ConditionType ="RANGE"+ MaxValue =48+ MinValue =24+ ObjectType ="CPUCoreRangeFilter"
}
+ Pids = []
+ SpeedRange = {
+ ConditionType ="RANGE"+ MaxValue =0+ MinValue =0+ ObjectType ="CpuSpeedRangeFilter"
}
+ Vendor =""
}
)
+ class_id ="resource.ProcessorQualifier"+ object_type ="resource.ProcessorQualifier"
},
+ {
+ class_id ="resource.DomainQualifier"+ object_type ="resource.DomainQualifier"
},
+ {
+ additional_properties =jsonencode(
{
+ GpuControllersRange = {
+ ConditionType ="RANGE"+ MaxValue =0+ MinValue =0+ ObjectType ="GpuControllersRangeFilter"
}
+ GpuEvaluationType ="ServerWithoutGpu"+ Pids = []
+ Vendor =""
}
)
+ class_id ="resource.GpuQualifier"+ object_type ="resource.GpuQualifier"
},
+ {
+ additional_properties =jsonencode(
{
+ MemoryCapacityRange = {
+ ConditionType ="RANGE"+ MaxValue =512+ MinValue =256+ ObjectType ="MemoryCapacityRangeFilter"
}
+ MemoryUnitsRange = {
+ ConditionType ="RANGE"+ MaxValue =0+ MinValue =0+ ObjectType ="MemoryUnitsRangeFilter"
}
}
)
+ class_id ="resource.MemoryQualifier"+ object_type ="resource.MemoryQualifier"
},
+ {
+ class_id ="resource.RackServerQualifier"+ object_type ="resource.RackServerQualifier"
},
+ {
+ class_id ="resource.TagQualifier"+ object_type ="resource.TagQualifier"
},
]
+resource_pools=(known after apply)
+shared_scope=(known after apply)
+tags=[]
+version_context=(known after apply)
}
Notice how the additional_properties is being stripped on the ObjectTypes that I listed above. But If I do a terraform import from an existing object in Intersight the Terraform configuration that I have above matches the import.
Bug Report Checklist
Description
When I run a plan I am finding that the resource intersight_resourcepool_qualification_policy is ignoring the additional_properties attributes for the following ObjectTypes:
It is working for the following ObjectTypes:
Terraform-provider-intersight version
Configuration file
Actual output (Attach screenshots if applicable)
Notice how the additional_properties is being stripped on the ObjectTypes that I listed above. But If I do a terraform import from an existing object in Intersight the Terraform configuration that I have above matches the import.
Related issues/PRs
Suggest a fix
The text was updated successfully, but these errors were encountered: