v3.8.0

3.8.0 (2023-05-11)

Features

• added a fix (by introducing new optional variable existing_ssh_key_name) to prevent SSH keys being identified for destroy due to regression introduced in v3.5.0 (#434) (19e26f3)

NOTES:

• For patterns that need an ssh key for configuration of a Virtual Server Instance (VSI), you can either create a new SSH Key resource, or use an existing resource, by doing the following:
  • to create a new SSH Key resource, supply the input variable ssh_public_key
  • to use an existing SSH Key resource in your account, supply the input variable existing_ssh_key_name
  • if neither value is supplied, and no keys are provided via override, a Terraform error will be thrown
• If you are using the override.json to provide SSH Keys:
  • to create new SSH Key resources, supply both "name" and "public_key" fields
  • to use existing keys, supply only "name" field