mirror of
https://github.com/opentffoundation/opentf.git
synced 2026-01-04 19:00:13 -05:00
8921e10d71
Here is an example that will setup the following:
+ An SSH key resource.
+ A virtual server resource that uses an existing SSH key.
+ A virtual server resource using an existing SSH key and a Terraform managed SSH key (created as "test_key_1" in the example below).
(create this as sl.tf and run terraform commands from this directory):
```hcl
provider "softlayer" {
username = ""
api_key = ""
}
resource "softlayer_ssh_key" "test_key_1" {
name = "test_key_1"
public_key = "${file(\"~/.ssh/id_rsa_test_key_1.pub\")}"
# Windows Example:
# public_key = "${file(\"C:\ssh\keys\path\id_rsa_test_key_1.pub\")}"
}
resource "softlayer_virtual_guest" "my_server_1" {
name = "my_server_1"
domain = "example.com"
ssh_keys = ["123456"]
image = "DEBIAN_7_64"
region = "ams01"
public_network_speed = 10
cpu = 1
ram = 1024
}
resource "softlayer_virtual_guest" "my_server_2" {
name = "my_server_2"
domain = "example.com"
ssh_keys = ["123456", "${softlayer_ssh_key.test_key_1.id}"]
image = "CENTOS_6_64"
region = "ams01"
public_network_speed = 10
cpu = 1
ram = 1024
}
```
You'll need to provide your SoftLayer username and API key,
so that Terraform can connect. If you don't want to put
credentials in your configuration file, you can leave them
out:
```
provider "softlayer" {}
```
...and instead set these environment variables:
- **SOFTLAYER_USERNAME**: Your SoftLayer username
- **SOFTLAYER_API_KEY**: Your API key
1.0 KiB
1.0 KiB
layout, page_title, sidebar_current, description
| layout | page_title | sidebar_current | description |
|---|---|---|---|
| softlayer | SoftLayer: ssh_key | docs-softlayer-resource-ssh-key | Manages SoftLayer SSH Keys. |
softlayer\ssh_key
Provides SSK keys. This allows SSH keys to be created, updated and deleted. For additional details please refer to API documentation.
Example Usage
resource "softlayer_ssh_key" "test_ssh_key" {
name = "test_ssh_key_name"
notes = "test_ssh_key_notes"
public_key = "ssh-rsa <rsa_public_key>"
}
Argument Reference
The following arguments are supported:
name- (Required) A descriptive name used to identify a ssh key.public_key- (Required) The public ssh key.notes- (Optional) A small note about a ssh key to use at your discretion.
Fields name and notes are editable.
Attributes Reference
The following attributes are exported:
id- id of the new ssh keyfingerprint- sequence of bytes to authenticate or lookup a longer ssh key.