Skip to content

Releases: DimensionDataResearch/terraform-provider-ddcloud

terraform-provider-ddcloud v1.2.0-beta3

14 Dec 20:48
Compare
Choose a tag to compare
Pre-release

This is an early release of v1.2 - it has undergone automated acceptance testing, and as far as we're aware nothing should be broken. It is almost ready for production use, but we need more user acceptance testing before we sign off on it. This is your last chance to provide feedback before we move to release candidates (which are bug-fix only).

Tested against Terraform v0.7.13 (also verified to work against v0.8.0-rc3, but only if built from source).

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).
  • The provider now prevents deployment of a ddcloud_server if it has multiple disk blocks with the same SCSI unit Id (#63).
  • Enable changing of adapter type for existing network adapters, where supported (#80).
  • Add new (experimental) ddcloud_ip_address_reservation resource type.
    This resource type allows specific IP addresses to be reserved on VLANs. It is only intended to support advanced usage scenarios.

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix crash when deploying a customer image using image_type="auto" (#66).
  • Fix INVALID_INPUT_DATA error when creating a ddcloud_address_list using complex addresses (#72).
  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2.0-beta2

12 Dec 08:47
Compare
Choose a tag to compare
Pre-release

This is an early release of v1.2 - it has undergone automated acceptance testing, and as far as we're aware nothing should be broken. It is not ready for production use, but it's ready for user acceptance testing.

Tested against Terraform v0.7.13 (also verified to work against v0.8.0-rc3, but only if built from source).

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).
  • The provider now prevents deployment of a ddcloud_server if it has multiple disk blocks with the same SCSI unit Id (#63).
  • Enable changing of adapter type for existing network adapters, where supported (#80).

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix crash when deploying a customer image using image_type="auto" (#66).
  • Fix INVALID_INPUT_DATA error when creating a ddcloud_address_list using complex addresses (#72).
  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2.0-beta1

07 Dec 06:34
Compare
Choose a tag to compare
Pre-release

This is an early release of v1.2 - it has undergone automated acceptance testing, and as far as we're aware nothing should be broken. It is not ready for production use, but it's ready for user acceptance testing.

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).
  • The provider now prevents deployment of a ddcloud_server if it has multiple disk blocks with the same SCSI unit Id (#63).

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix crash when deploying a customer image using image_type="auto" (#66).
  • Fix INVALID_INPUT_DATA error when creating a ddcloud_address_list using complex addresses (#72).
  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2.0-alpha4

07 Dec 04:25
Compare
Choose a tag to compare

This is an early release of v1.2 - it has undergone basic smoke-testing, but things may still be broken. It is not ready for production use.

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix crash when deploying a customer image using image_type="auto" (#66).
  • Fix INVALID_INPUT_DATA error when creating a ddcloud_address_list using complex addresses (#72).
  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2.0-alpha3

06 Dec 07:38
Compare
Choose a tag to compare

This is an early release of v1.2 - it has undergone basic smoke-testing, but things may still be broken. It is not ready for production use.

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix INVALID_INPUT_DATA error when creating a ddcloud_address_list using complex addresses (#72).
  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.1.10

06 Dec 03:57
Compare
Choose a tag to compare

Bug fixes

  • Fix incorrect schema for simple port list on ddcloud_port_list (#71).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2.0-alpha1

05 Dec 22:28
Compare
Choose a tag to compare

This is an early release of v1.2 - it has undergone basic smoke-testing, but things may still be broken. It is not ready for production use.

Enhancements

  • Add the ability to manage default firewall rules (#54)
  • The provider now automatically retries CloudControl operations (where appropriate) that fail due to a RESOURCE_BUSY response (#11)
  • Use default DNS when deploying a server if no specific DNS IPs are configured (#62)
  • Network adapters are added to server as part of initial deployment rather than having to wait until after deployment to add them (#56).
  • Fix UNEXPECTED_ERROR responses from CloudControl due to simultaneously initiating multiple asynchronous operations
    Multiple asynchronous operations can run in parallel, but only 1 can be initiated at a time
  • Disk speed is now applied to disks that are part of the initial deployment.
  • MAC address is now exposed on network adapters.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set this single property (and there's an optional second property if you want to customise behaviour). Specify the image name or Id, and the provider will automatically resolve the correct image.
    • You can customise behaviour via the image_type property:
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - (Default) Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).

Breaking changes

Note: If you have existing terraform.tfstate files, their contents may need to be updated to match the new provider schema. We haven't written documentation on migrating to v1.2 yet, but when we do this will include instructions on how to do this. For now, we'd recommend that you avoid using this release against existing state files from v1.1.

  • retry_count and retry_delay provider properties have been removed (use the MCP_MAX_RETRY and MCP_RETRY_DELAY environment variables instead)
    retry_delay is now used to control retry of operations that fail due to a RESOURCE_BUSY response from CloudControl
  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both).
    Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.
  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fix crash when deploying ddcloud_server from a customer image (#66).

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2-preview5

03 Dec 23:55
Compare
Choose a tag to compare

This is a preview release intended to gather feedback on changes to ddcloud_server.primary_network_adapter, ddcloud_server.additional_network_adapter, and ddcloud_network_adapter.


Enhancements

  • MAC address is now exposed on network adapters.

Breaking changes

  • Primary network adapter is now exposed via ddcloud_server.primary_network_adapter (#56).
  • Additional network adapters are now exposed via ddcloud_server.additional_network_adapter and ddcloud_network_adapter (#56).
    Note: You can specify additional adapters for a given ddcloud_server via either the ddcloud_server.additional_network_adapter or ddcloud_network_adapter (but not both). Use ddcloud_network_adapter if you want to be able to modify additional network adapters after deployment.

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2-preview4

02 Dec 02:56
Compare
Choose a tag to compare

This is a preview release intended to gather feedback on changes to ddcloud_server.image and ddcloud_server.admin_password.


Enhancements

  • The provider will now attempt to automatically migrate the data for ddcloud_server.disk from a Set to a List.
    Note - if you have not used v1.2-preview3, then you can now disregard the warning about terraform.tfstate incompatibility.
  • The image for a ddcloud_server is now configured via ddcloud_server.image (#66).
    You now only need to set 1 of 2 properties (and there's an optional 3rd property if you want to customise behaviour). See the provider documentation for details.
    • id - The Id of the target image to use.
    • name - The name of the target image to use.
    • type - The type of image to use (optional, defaults to auto).
      • os - Use an OS image with the specified Id or name.
      • customer - Use an OS image with the specified Id or name.
      • auto - Use an OS or customer image with the specified Id or name (auto-detect image type).
        Note that if an OS and customer image have the same name or Id, the OS image will be used.
  • ddcloud_server.admin_password is now optional for server images that don't require an initial administrator password (#65).

Breaking changes

  • ddcloud_server properties relating to image have been moved into ddcloud_server.image (#66).

Bug fixes

  • Fixed crash when deploying a ddcloud_server.

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.

terraform-provider-ddcloud v1.2-preview3

01 Dec 07:44
Compare
Choose a tag to compare

This is a preview release intended to gather feedback on changes to ddcloud_server.disk and ddcloud_server._network_adapter behaviour.

Breaking changes

  • Network adapters now modelled as ddcloud_server.network_adapter (see documentation on ddcloud_server resource type for details).
  • Change ddcloud_server.disk from a set to a list in order to fix errors when performing subsequent terraform apply that modifies an existing disk (#63).
    Note - this will break any existing terraform.tfstate values you have for ddcloud_server resources.

Getting started

  • Choose the appropriate executable for your OS
  • Copy it to the same directory as the main Terraform executable.
  • If your .terraformrc / terraform.rc file contains the following configuration, remove it (no longer required):
providers {
    ddcloud = "path-to-the-folder/containing/dd-cloud-compute-terraform/terraform-provider-ddcloud(.exe)"
}

For more information, see the documentation and change log.