Skip to content

Instantly share code, notes, and snippets.

@fgionghi

fgionghi/gist:ac817c95552e260b52d18f6ce2924887

Created October 11, 2021 09:13
Show Gist options
  • Save fgionghi/ac817c95552e260b52d18f6ce2924887 to your computer and use it in GitHub Desktop.
Save fgionghi/ac817c95552e260b52d18f6ce2924887 to your computer and use it in GitHub Desktop.
Download ZIP
Ouput plan
Raw
gistfile1.txt
Running with gitlab-runner 14.3.2 (e0218c92)
 on salt-server xPrAqZXH
section_start:1633942985:resolve_secrets
Resolving secrets
section_end:1633942985:resolve_secrets
section_start:1633942985:prepare_executor
Preparing the "shell" executor
Using Shell executor...
section_end:1633942985:prepare_executor
section_start:1633942985:prepare_script
Preparing environment
Running on salt-server...
section_end:1633942985:prepare_script
section_start:1633942985:get_sources
Getting source from Git repository
Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /home/gitlab-runner/builds/xPrAqZXH/0/terraform/datacenter/vmware/bind-mv/.git/
Checking out b01c2511 as main...
Removing .terraform.lock.hcl
Removing .terraform/
Skipping Git submodules setup
section_end:1633942986:get_sources
section_start:1633942986:step_script
Executing "step_script" stage of the job script
$ tfenv install
Terraform v1.0.8 is already installed
$ terraform init
Initializing the backend...

Successfully configured the backend "local"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Finding hashicorp/vsphere versions matching "2.0.2"...
- Finding infobloxopen/infoblox versions matching ">= 2.0.1"...
- Installing hashicorp/vsphere v2.0.2...
- Installed hashicorp/vsphere v2.0.2 (signed by HashiCorp)
- Installing infobloxopen/infoblox v2.0.1...
- Installed infobloxopen/infoblox v2.0.1 (signed by a HashiCorp partner, key ID B355854AA5DBB18E)
Partner and community providers are signed by their developers.
If you'd like to know more about provider signing, you can read about it here:
https://www.terraform.io/docs/cli/plugins/signing.html
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
$ terraform plan
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:
 # vsphere_virtual_machine.vm will be created
 + resource "vsphere_virtual_machine" "vm" {
+ boot_retry_delay = 10000
+ change_version = (known after apply)
+ cpu_limit = -1
+ cpu_share_count = (known after apply)
+ cpu_share_level = "normal"
+ datastore_cluster_id = "group-p181392"
+ datastore_id = (known after apply)
+ default_ip_address = (known after apply)
+ ept_rvi_mode = "automatic"
+ firmware = "bios"
+ folder = "fbkdc/vm/terraform/services"
+ force_power_off = true
+ guest_id = "ubuntu64Guest"
+ guest_ip_addresses = (known after apply)
+ hardware_version = (known after apply)
+ host_system_id = (known after apply)
+ hv_mode = "hvAuto"
+ id = (known after apply)
+ ide_controller_count = 2
+ imported = (known after apply)
+ latency_sensitivity = "normal"
+ memory = 1024
+ memory_limit = -1
+ memory_share_count = (known after apply)
+ memory_share_level = "normal"
+ migrate_wait_timeout = 30
+ moid = (known after apply)
+ name = "mydyndns"
+ num_cores_per_socket = 1
+ num_cpus = 1
+ poweron_timeout = 300
+ reboot_required = (known after apply)
+ resource_pool_id = "resgroup-334415"
+ run_tools_scripts_after_power_on = true
+ run_tools_scripts_after_resume = true
+ run_tools_scripts_before_guest_shutdown = true
+ run_tools_scripts_before_guest_standby = true
+ sata_controller_count = 0
+ scsi_bus_sharing = "noSharing"
+ scsi_controller_count = 1
+ scsi_type = "pvscsi"
+ shutdown_wait_timeout = 3
+ storage_policy_id = (known after apply)
+ swap_placement_policy = "inherit"
+ uuid = (known after apply)
+ vapp_transport = (known after apply)
+ vmware_tools_status = (known after apply)
+ vmx_path = (known after apply)
+ wait_for_guest_ip_timeout = 0
+ wait_for_guest_net_routable = true
+ wait_for_guest_net_timeout = 5
+ clone {
+ template_uuid = "42008eba-6eea-2ef4-4071-2b265afb4e90"
+ timeout = 30
+ customize {
+ dns_server_list = [
+ "217.77.80.4",
+ "217.77.80.13",
]
+ ipv4_gateway = "217.77.83.254"
+ timeout = 10
+ linux_options {
+ domain = "fbk.eu"
+ host_name = "mydyndns"
+ hw_clock_utc = true
}
+ network_interface {
+ ipv4_address = "217.77.83.6"
+ ipv4_netmask = 24
}
}
}
+ disk {
+ attach = false
+ controller_type = "scsi"
+ datastore_id = "<computed>"
+ device_address = (known after apply)
+ disk_mode = "persistent"
+ disk_sharing = "sharingNone"
+ eagerly_scrub = false
+ io_limit = -1
+ io_reservation = 0
+ io_share_count = 0
+ io_share_level = "normal"
+ keep_on_remove = false
+ key = 0
+ label = "disk0"
+ path = (known after apply)
+ size = 30
+ storage_policy_id = (known after apply)
+ thin_provisioned = true
+ unit_number = 0
+ uuid = (known after apply)
+ write_through = false
}
+ network_interface {
+ adapter_type = "vmxnet3"
+ bandwidth_limit = -1
+ bandwidth_reservation = 0
+ bandwidth_share_count = (known after apply)
+ bandwidth_share_level = "normal"
+ device_address = (known after apply)
+ key = (known after apply)
+ mac_address = (known after apply)
+ network_id = "dvportgroup-306"
}
}
Plan: 1 to add, 0 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────
Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.
section_end:1633942992:step_script
section_start:1633942992:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1633942992:cleanup_file_variables
Job succeeded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment