Add terraform import support for several cloudstack resources - #305
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request adds Terraform import support across a set of CloudStack provider resources by wiring in Importer blocks (including project-aware passthrough where needed), introducing a few custom import state resolvers (e.g., for resources that Read-by-name or that need to materialize nested rule sets), and documenting the expected import IDs. It also adds/extends acceptance tests to validate import behavior for several of the updated resources.
Changes:
- Added
Importersupport to multiple resources, using either passthrough import or custom import-state functions where an ID-to-name (or ID-to-ruleset) translation is required. - Implemented custom import logic for port-forwarding rules and for offerings that are read back by name (service/network offerings).
- Added import documentation sections and import acceptance tests for several resources.
Reviewed changes
Copilot reviewed 30 out of 30 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| website/docs/r/vpn_connection.html.markdown | Documents cloudstack_vpn_connection import usage. |
| website/docs/r/static_nat.html.markdown | Documents cloudstack_static_nat import usage, including project-prefixed IDs. |
| website/docs/r/port_forward.html.markdown | Documents cloudstack_port_forward import behavior and managed-rule import semantics. |
| website/docs/r/loadbalancer_rule.html.markdown | Documents cloudstack_loadbalancer_rule import usage and write-only field caveat. |
| website/docs/r/ipaddress.html.markdown | Documents cloudstack_ipaddress import usage, including project-prefixed IDs. |
| website/docs/r/counter.html.markdown | Documents cloudstack_counter import usage. |
| website/docs/r/condition.html.markdown | Documents cloudstack_condition import usage. |
| website/docs/r/autoscale_vm_profile.html.markdown | Documents cloudstack_autoscale_vm_profile import usage. |
| website/docs/r/autoscale_policy.html.markdown | Documents cloudstack_autoscale_policy import usage. |
| cloudstack/resource_cloudstack_vpn_connection.go | Adds passthrough importer for VPN connections. |
| cloudstack/resource_cloudstack_vpn_connection_test.go | Adds acceptance import test for VPN connections. |
| cloudstack/resource_cloudstack_static_nat.go | Enables project-aware passthrough import for static NAT. |
| cloudstack/resource_cloudstack_static_nat_test.go | Adds acceptance import test for static NAT. |
| cloudstack/resource_cloudstack_service_offering.go | Adds importer that resolves offering name from ID before refresh. |
| cloudstack/resource_cloudstack_service_offering_test.go | Adds acceptance import test for service offerings. |
| cloudstack/resource_cloudstack_port_forward.go | Adds custom importer that imports all port forwarding rules for an IP into the forward set and forces managed=true. |
| cloudstack/resource_cloudstack_port_forward_test.go | Adds acceptance import test for port forwards (ignoring managed). |
| cloudstack/resource_cloudstack_network_offering.go | Adds importer that resolves network offering name from ID before refresh. |
| cloudstack/resource_cloudstack_loadbalancer_rule.go | Enables project-aware passthrough import for load balancer rules. |
| cloudstack/resource_cloudstack_loadbalancer_rule_test.go | Adds acceptance import test for load balancer rules (ignoring certificate_id). |
| cloudstack/resource_cloudstack_ipaddress.go | Enables project-aware passthrough import for IP addresses. |
| cloudstack/resource_cloudstack_ipaddress_test.go | Adds acceptance import test for IP addresses. |
| cloudstack/resource_cloudstack_host.go | Adds passthrough importer for hosts. |
| cloudstack/resource_cloudstack_host_test.go | Adds acceptance import test for hosts with appropriate ignore list for write-only/provider-local fields. |
| cloudstack/resource_cloudstack_counter.go | Adds passthrough importer for counters. |
| cloudstack/resource_cloudstack_condition.go | Adds passthrough importer for conditions. |
| cloudstack/resource_cloudstack_autoscale_vm_profile.go | Adds passthrough importer for autoscale VM profiles. |
| cloudstack/resource_cloudstack_autoscale_vm_profile_test.go | Adds import acceptance test but currently skips it unconditionally. |
| cloudstack/resource_cloudstack_autoscale_vm_group.go | Adds passthrough importer for autoscale VM groups. |
| cloudstack/resource_cloudstack_autoscale_policy.go | Adds passthrough importer for autoscale policies. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| func TestAccCloudStackAutoscaleVMProfile_import(t *testing.T) { | ||
| t.Skip("Skipping due to bug in cloudstack-go library") | ||
|
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 30 out of 30 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (3)
cloudstack/resource_cloudstack_autoscale_vm_profile_test.go:90
- This acceptance test is unconditionally skipped, so the new import support for
cloudstack_autoscale_vm_profileisn’t exercised in CI and regressions won’t be caught. If there’s an upstream cloudstack-go issue, consider making the skip conditional (only for affected CloudStack/cloudstack-go versions) and/or referencing a tracking issue so it’s clear when it can be re-enabled.
func TestAccCloudStackAutoscaleVMProfile_import(t *testing.T) {
t.Skip("Skipping due to bug in cloudstack-go library")
website/docs/r/vpn_connection.html.markdown:46
- The example import ID isn’t a valid UUID (the first group has 7 hex characters). Using an invalid-looking ID makes the copy/paste example confusing; use an 8-4-4-4-12 UUID format in the example.
VPN Connections can be imported using the `id`, e.g.
```shell
$ terraform import cloudstack_vpn_connection.default 6eb22f91-7454-4107-89f4-36afcdf33021
**website/docs/r/counter.html.markdown:51**
* The example import ID isn’t a valid UUID (the first group has 7 hex characters). Using an invalid-looking ID makes the copy/paste example confusing; use an 8-4-4-4-12 UUID format in the example.
Counters can be imported using the id, e.g.
$ terraform import cloudstack_counter.default 6eb22f91-7454-4107-89f4-36afcdf33021</details>
| // Try to split the ID to extract the optional project name. | ||
| s := strings.SplitN(d.Id(), "/", 2) | ||
| if len(s) == 2 { | ||
| d.Set("project", s[0]) | ||
| } | ||
|
|
||
| ipAddressID := s[len(s)-1] | ||
| d.SetId(ipAddressID) | ||
|
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 30 out of 30 changed files in this pull request and generated 7 comments.
Comments suppressed due to low confidence (1)
cloudstack/resource_cloudstack_autoscale_vm_profile_test.go:90
- The newly added import acceptance test is unconditionally skipped, so the PR adds import functionality without any automated validation. Either make the skip conditional (e.g., only for specific CloudStack versions) or link to the upstream cloudstack-go issue and track removing the skip so import stays covered.
func TestAccCloudStackAutoscaleVMProfile_import(t *testing.T) {
t.Skip("Skipping due to bug in cloudstack-go library")
| *NOTE: All existing port forwarding rules for the IP address are imported into | ||
| a single `forward` set, and `managed` is set to `true` so unrelated rules | ||
| created outside of this resource aren't dropped on the next apply.* |
| d.Set("forward", forwards) | ||
| d.Set("managed", true) | ||
|
|
||
| return []*schema.ResourceData{d}, nil |
| // The importer sets managed=true so unrelated forwards on the same IP | ||
| // aren't silently dropped; the applied config leaves it at its default. | ||
| ImportStateVerifyIgnore: []string{"managed"}, |
| Importer: &schema.ResourceImporter{ | ||
| State: resourceCloudStackServiceOfferingImport, | ||
| }, |
| Importer: &schema.ResourceImporter{ | ||
| State: resourceCloudStackNetworkOfferingImport, | ||
| }, |
| Importer: &schema.ResourceImporter{ | ||
| State: schema.ImportStatePassthrough, | ||
| }, |
| ## Import | ||
|
|
||
| Autoscale VM profiles can be imported using the `id`, e.g. | ||
|
|
||
| ```shell | ||
| $ terraform import cloudstack_autoscale_vm_profile.default 6eb22f91-7454-4107-89f4-36afcdf33021 | ||
| ``` |
663fbb5 to
57ef4b1
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 30 out of 30 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (6)
cloudstack/resource_cloudstack_autoscale_vm_profile_test.go:89
- This import acceptance test is currently always skipped, which means the new import functionality won’t be exercised in CI. Please include a specific upstream issue/PR reference in the skip message so it’s easy to track when it can be re-enabled.
t.Skip("Skipping due to bug in cloudstack-go library")
website/docs/r/vpn_connection.html.markdown:46
- The example import ID is not a valid UUID (it’s missing a leading hex digit). This can break copy/paste usage; use a properly formatted UUID in the example.
VPN Connections can be imported using the `id`, e.g.
```shell
$ terraform import cloudstack_vpn_connection.default eb22f91-7454-4107-89f4-36afcdf33021
**website/docs/r/counter.html.markdown:51**
* The example import ID is not a valid UUID (it’s missing a leading hex digit). This can break copy/paste usage; use a properly formatted UUID in the example.
Counters can be imported using the id, e.g.
$ terraform import cloudstack_counter.default eb22f91-7454-4107-89f4-36afcdf33021**website/docs/r/condition.html.markdown:69**
* The example import ID is not a valid UUID (it’s missing a leading hex digit). This can break copy/paste usage; use a properly formatted UUID in the example.
Conditions can be imported using the id, e.g.
$ terraform import cloudstack_condition.default eb22f91-7454-4107-89f4-36afcdf33021**website/docs/r/autoscale_vm_profile.html.markdown:84**
* The example import ID is not a valid UUID (it’s missing a leading hex digit). This can break copy/paste usage; use a properly formatted UUID in the example.
Autoscale VM profiles can be imported using the id, e.g.
$ terraform import cloudstack_autoscale_vm_profile.default eb22f91-7454-4107-89f4-36afcdf33021**website/docs/r/autoscale_policy.html.markdown:71**
* The example import ID is not a valid UUID (it’s missing a leading hex digit). This can break copy/paste usage; use a properly formatted UUID in the example.
Autoscale policies can be imported using the id, e.g.
$ terraform import cloudstack_autoscale_policy.default eb22f91-7454-4107-89f4-36afcdf33021</details>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 32 out of 32 changed files in this pull request and generated no new comments.
Suppressed comments (7)
website/docs/r/vpn_connection.html.markdown:45
- The example import ID is not a valid UUID (first segment is 7 chars). This can confuse users copying the command; use a valid UUID format or a placeholder.
website/docs/r/counter.html.markdown:50 - The example import ID is not a valid UUID (first segment is 7 chars). Use a valid UUID format or a placeholder to avoid copy/paste failures.
$ terraform import cloudstack_counter.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/condition.html.markdown:68
- The example import ID is not a valid UUID (first segment is 7 chars). Use a valid UUID format or a placeholder to avoid copy/paste failures.
$ terraform import cloudstack_condition.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/autoscale_policy.html.markdown:70
- The example import ID is not a valid UUID (first segment is 7 chars). Use a valid UUID format or a placeholder to avoid copy/paste failures.
$ terraform import cloudstack_autoscale_policy.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/autoscale_vm_profile.html.markdown:83
- The example import ID is not a valid UUID (first segment is 7 chars). Use a valid UUID format or a placeholder to avoid copy/paste failures.
$ terraform import cloudstack_autoscale_vm_profile.default eb22f91-7454-4107-89f4-36afcdf33021
cloudstack/resource_cloudstack_autoscale_vm_profile_test.go:90
- This new import acceptance test is unconditionally skipped, but the skip reason doesn’t reference any upstream issue/PR. Adding a link or issue ID would make it easier to track and remove the skip when cloudstack-go is fixed.
func TestAccCloudStackAutoscaleVMProfile_import(t *testing.T) {
t.Skip("Skipping due to bug in cloudstack-go library")
website/docs/r/autoscale_vm_profile.html.markdown:87
- This note mentions an "upstream cloudstack-go issue" but doesn’t link to (or name) the specific issue/PR. Adding a reference would help users and maintainers understand when this limitation is expected to be resolved.
*NOTE: Import acceptance test coverage is currently skipped due to an upstream
cloudstack-go issue.*
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 32 out of 32 changed files in this pull request and generated no new comments.
Suppressed comments (7)
website/docs/r/vpn_connection.html.markdown:45
- The example import ID doesn't match the UUID format (the first segment is 7 chars). Using a valid UUID-shaped example avoids confusion when users copy/paste.
website/docs/r/autoscale_vm_profile.html.markdown:83 - The example import ID doesn't match the UUID format (the first segment is 7 chars). Using a valid UUID-shaped example avoids confusion when users copy/paste.
$ terraform import cloudstack_autoscale_vm_profile.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/counter.html.markdown:50
- The example import ID doesn't match the UUID format (the first segment is 7 chars). Using a valid UUID-shaped example avoids confusion when users copy/paste.
$ terraform import cloudstack_counter.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/condition.html.markdown:68
- The example import ID doesn't match the UUID format (the first segment is 7 chars). Using a valid UUID-shaped example avoids confusion when users copy/paste.
$ terraform import cloudstack_condition.default eb22f91-7454-4107-89f4-36afcdf33021
website/docs/r/autoscale_policy.html.markdown:70
- The example import ID doesn't match the UUID format (the first segment is 7 chars). Using a valid UUID-shaped example avoids confusion when users copy/paste.
$ terraform import cloudstack_autoscale_policy.default eb22f91-7454-4107-89f4-36afcdf33021
cloudstack/resource_cloudstack_ipaddress.go:222
- When the IP address is not associated with a network (e.g., zone-only non-portable IPs), ip.Associatednetworkid can be empty. Setting network_id unconditionally in that case can leave an empty string in state and cause perpetual diffs (especially since network_id is ForceNew). Only set network_id when the API returns a non-empty Associatednetworkid.
if ip.Vpcid != "" {
d.Set("vpc_id", ip.Vpcid)
} else {
d.Set("network_id", ip.Associatednetworkid)
}
cloudstack/resource_cloudstack_host.go:241
- allocation_state is being populated from h.Resourcestate, which duplicates resource_state and will store the wrong value in state. This should come from the host's allocation state field instead.
"allocation_state": h.Resourcestate,
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 32 out of 32 changed files in this pull request and generated no new comments.
Suppressed comments (3)
website/docs/r/service_offering.html.markdown:111
- This note says the required
nameattribute “does not need to be set in the configuration beforehand”, but in the provider schemanameis stillRequired: true. As written, this is misleading for users (Terraform config validation / subsequent plan/apply will still requirenameto be set).
*NOTE: The importer looks up the service offering by ID and resolves the
required `name` attribute from it, so it does not need to be set in the
configuration beforehand.*
cloudstack/resource_cloudstack_host.go:241
allocation_stateis being populated fromh.Resourcestate, which is a different CloudStack field than allocation state. This will misreport the allocation state in state and can cause incorrect diffs/updates when users manageallocation_state.
"allocation_state": h.Resourcestate,
website/docs/r/network_offering.html.markdown:84
- This note says the required
nameattribute “does not need to be set in the configuration beforehand”, but in the provider schemanameis stillRequired: true. As written, this is misleading for users (Terraform config validation / subsequent plan/apply will still requirenameto be set).
*NOTE: The importer looks up the network offering by ID and resolves the
required `name` attribute from it, so it does not need to be set in the
configuration beforehand.*
| "zone_id": h.Zoneid, | ||
| "state": h.State, | ||
| "resource_state": h.Resourcestate, | ||
| "allocation_state": h.Resourcestate, |
There was a problem hiding this comment.
"resource_state" and "allocation_state" both are set as h.Resourcestate
confirm if this is correct?
kiranchavala
left a comment
There was a problem hiding this comment.
LGTM , Tested manually
#1. cloudstack_autoscale_policy
resource "cloudstack_autoscale_policy" "scale_up_policy" {
name = "scale-up-policy"
action = "scaleup" # Case insensitive: scaleup/SCALEUP
duration = 300 # 5 minutes
quiet_time = 300 # 5 minutes
condition_ids = [cloudstack_condition.scale_up_condition.id]
}
#2. cloudstack_autoscale_vm_profile
resource "cloudstack_autoscale_vm_profile" "profile1" {
service_offering = "small"
template = "CentOS 6.5"
zone = "zone-1"
destroy_vm_grace_period = "45s"
other_deploy_params = {
networkids = "6eb22f91-7454-4107-89f4-36afcdf33021"
displayname = "profile1vm"
}
metadata = {
mydata = "true"
}
}
#3. cloudstack_condition
resource "cloudstack_condition" "scale_up_condition" {
counter_id = data.cloudstack_counter.cpu_counter.id
relational_operator = "GT"
threshold = 80.0
account_name = "admin"
domain_id = "1"
}
#4. cloudstack_counter
resource "cloudstack_counter" "cpu_counter" {
name = "cpu-counter"
source = "cpu"
value = "cpuused"
}
#5. cloudstack_ipaddress
resource "cloudstack_ipaddress" "default" {
network_id = "6eb22f91-7454-4107-89f4-36afcdf33021"
}
#6. cloudstack_loadbalancer_rule
resource "cloudstack_loadbalancer_rule" "default" {
name = "loadbalancer-rule-1"
description = "Loadbalancer rule 1"
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
algorithm = "roundrobin"
private_port = 80
public_port = 80
member_ids = ["f8141e2f-4e7e-4c63-9362-986c908b7ea7"]
cidrlist = ["12.34.56.78/30", "99.99.99.99/32"]
}
#7. cloudstack_network_offering
resource "cloudstack_network_offering" "example" {
name = "example-network-offering"
display_text = "Example Network Offering"
guest_ip_type = "Isolated"
traffic_type = "Guest"
network_rate = 100
network_mode = "NATTED"
conserve_mode = true
enable = true
for_vpc = false
specify_vlan = true
specify_ip_ranges = true
max_connections = 256
supported_services = ["Dhcp", "Dns", "Firewall", "Lb", "SourceNat"]
service_provider_list = {
Dhcp = "VirtualRouter"
Dns = "VirtualRouter"
Firewall = "VirtualRouter"
Lb = "VirtualRouter"
SourceNat = "VirtualRouter"
}
}
#8. cloudstack_port_forward
resource "cloudstack_port_forward" "default" {
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
forward {
protocol = "tcp"
private_port = 80
public_port = 8080
virtual_machine_id = "f8141e2f-4e7e-4c63-9362-986c908b7ea7"
}
}
#9. cloudstack_service_offering
resource "cloudstack_service_offering" "example" {
name = "example-service-offering"
display_text = "Example Service Offering"
cpu_number = 2
memory = 4096
}
#10. cloudstack_static_nat
resource "cloudstack_static_nat" "default" {
ip_address_id = "f8141e2f-4e7e-4c63-9362-986c908b7ea7"
virtual_machine_id = "6ca2a163-bc68-429c-adc8-ab4a620b1bb3"
}
#11. cloudstack_vpn_connection
resource "cloudstack_vpn_connection" "default" {
customer_gateway_id = "8dab9381-ae73-48b8-9a3d-c460933ef5f7"
vpn_gateway_id = "a7900060-f8a8-44eb-be15-ea54cf499703"
}
1. cloudstack_autoscale_policy.scale_up_policy
terraform import cloudstack_autoscale_policy.scale_up_policy 4623ed8d-7c54-4047-a343-537b39aa9e10
cloudstack_autoscale_policy.scale_up_policy: Importing from ID "4623ed8d-7c54-4047-a343-537b39aa9e10"...
cloudstack_autoscale_policy.scale_up_policy: Import prepared!
Prepared cloudstack_autoscale_policy for import
cloudstack_autoscale_policy.scale_up_policy: Refreshing state... [id=4623ed8d-7c54-4047-a343-537b39aa9e10]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
2.cloudstack_autoscale_vm_profile.profile1
terraform import cloudstack_autoscale_vm_profile.profile1 67d9fb70-a783-46ca-b647-9f278eb5a359
cloudstack_autoscale_vm_profile.profile1: Importing from ID "67d9fb70-a783-46ca-b647-9f278eb5a359"...
cloudstack_autoscale_vm_profile.profile1: Import prepared!
Prepared cloudstack_autoscale_vm_profile for import
cloudstack_autoscale_vm_profile.profile1: Refreshing state... [id=67d9fb70-a783-46ca-b647-9f278eb5a359]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
3. cloudstack_condition.scale_up_condition
terraform import cloudstack_condition.scale_up_condition 8655e6ab-dc07-432a-87e4-7f806769bd46
cloudstack_condition.scale_up_condition: Importing from ID "8655e6ab-dc07-432a-87e4-7f806769bd46"...
cloudstack_condition.scale_up_condition: Import prepared!
Prepared cloudstack_condition for import
cloudstack_condition.scale_up_condition: Refreshing state... [id=8655e6ab-dc07-432a-87e4-7f806769bd46]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
4. cloudstack_counter
terraform import cloudstack_counter.cpu_counter 79c52b1b-6648-11f1-afab-bc2411acabdc
cloudstack_counter.cpu_counter: Importing from ID "79c52b1b-6648-11f1-afab-bc2411acabdc"...
cloudstack_counter.cpu_counter: Import prepared!
Prepared cloudstack_counter for import
cloudstack_counter.cpu_counter: Refreshing state... [id=79c52b1b-6648-11f1-afab-bc2411acabdc]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
5. cloudstack_ipaddress
terraform import cloudstack_ipaddress.default 14d1e59a-4b21-4e88-a93b-0b9f4cd712c9
cloudstack_ipaddress.default: Importing from ID "14d1e59a-4b21-4e88-a93b-0b9f4cd712c9"...
cloudstack_ipaddress.default: Import prepared!
Prepared cloudstack_ipaddress for import
cloudstack_ipaddress.default: Refreshing state... [id=14d1e59a-4b21-4e88-a93b-0b9f4cd712c9]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
6. cloudstack_loadbalancer_rule
terraform import cloudstack_loadbalancer_rule.default d42d30fc-c3f9-4951-a60a-481d72d90fe2
cloudstack_loadbalancer_rule.default: Importing from ID "d42d30fc-c3f9-4951-a60a-481d72d90fe2"...
cloudstack_loadbalancer_rule.default: Import prepared!
Prepared cloudstack_loadbalancer_rule for import
cloudstack_loadbalancer_rule.default: Refreshing state... [id=d42d30fc-c3f9-4951-a60a-481d72d90fe2]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
7. cloudstack_network_offering
terraform import cloudstack_network_offering.example 81620bf5-2c76-4c86-aab5-1032b3b561bf
cloudstack_network_offering.example: Importing from ID "81620bf5-2c76-4c86-aab5-1032b3b561bf"...
cloudstack_network_offering.example: Import prepared!
Prepared cloudstack_network_offering for import
cloudstack_network_offering.example: Refreshing state... [id=81620bf5-2c76-4c86-aab5-1032b3b561bf]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
8. cloudstack_port_forward
terraform import cloudstack_port_forward.default 14d1e59a-4b21-4e88-a93b-0b9f4cd712c9
cloudstack_port_forward.default: Importing from ID "14d1e59a-4b21-4e88-a93b-0b9f4cd712c9"...
cloudstack_port_forward.default: Import prepared!
Prepared cloudstack_port_forward for import
cloudstack_port_forward.default: Refreshing state... [id=14d1e59a-4b21-4e88-a93b-0b9f4cd712c9]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform
9. cloudstack_service_offering
terraform import cloudstack_service_offering.example e79bb1db-617b-4f35-bbef-7f5d452fa0af
cloudstack_service_offering.example: Importing from ID "e79bb1db-617b-4f35-bbef-7f5d452fa0af"...
cloudstack_service_offering.example: Import prepared!
Prepared cloudstack_service_offering for import
cloudstack_service_offering.example: Refreshing state... [id=e79bb1db-617b-4f35-bbef-7f5d452fa0af]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
10 . cloudstack_static_nat
terraform import cloudstack_static_nat.default aa331f9d-8246-4ad7-86cd-455560864cb3
cloudstack_static_nat.default: Importing from ID "aa331f9d-8246-4ad7-86cd-455560864cb3"...
cloudstack_static_nat.default: Import prepared!
Prepared cloudstack_static_nat for import
cloudstack_static_nat.default: Refreshing state... [id=aa331f9d-8246-4ad7-86cd-455560864cb3]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
11. cloudstack_vpn_connection
terraform import cloudstack_vpn_connection.default 4b02903b-d417-4ca1-b983-acd95e321a1d
cloudstack_vpn_connection.default: Importing from ID "4b02903b-d417-4ca1-b983-acd95e321a1d"...
cloudstack_vpn_connection.default: Import prepared!
Prepared cloudstack_vpn_connection for import
cloudstack_vpn_connection.default: Refreshing state... [id=4b02903b-d417-4ca1-b983-acd95e321a1d]
Import successful!
The resources that were imported are shown above. These resources are now in
your Terraform state and will henceforth be managed by Terraform.
No description provided.