Releases: delphix-integrations/terraform-provider-delphix
v3.3.0
Terraform Provider for Delphix v3.3.0
This release includes the following change:
- The VDB (
delphix_vdb
) resource will now accept and apply property updates to the resource. This enables drift detection and update-in-place functionality for these resources. - The VDB resource’s
instance_name
property will now specify the Oracle System Identifier (SID) value if applicable.(available starting DCT v22+) - The PostgreSQL Database (
delphix_database_postgresql
) resource can now import existing PostgreSQL source configs. - [Beta] The VDB (
delphix_vdb
) resource can now import existing virtual databases.
This is a beta feature and therefore, we offer no guarantees of support. It will be made generally available in a future release.
v3.2.3
Terraform Provider for Delphix v3.2.3
This release includes the following change:
- Added the
masked
argument to thedelphix_vdb
resource to set the virtual database's masked status. The masking job is then initiated through the use of a VDB hook.
v3.2.2
Terraform Provider for Delphix v3.2.2
This release fixes the following bug:
- Removing computed attribute
storage_size
, as this is not a required attribute in the infrastructure-as-code use case.
v3.2.1
Terraform Provider for Delphix v3.2.1
This release fixes the following bug:
- Upgrade from 3.1.0 -> 3.2.0 was causing failure due to a drift identified in the newly introduced
wait_time
variable, to fix this we have set the default value for wait_time to 0.
v3.2.0
Terraform Provider for Delphix v3.2.0
This release adds the following new features:
-
A new Terraform resource
delphix_database_postgresql
to support adding Database (or Source Config) for PostgreSql. -
dSource: Wait for sync to complete i.e snapshot creation.
-
Terraform SDK upgrade to V2.
-
MySql examples for dsource and vdb
v3.1.0
Terraform Provider for Delphix v3.1.0
This release adds the following new features:
-
A new Terraform resource to support the linking of data sources managed by Oracle.
-
dSource: delphix_oracle_dsource , SQL Server and SAP ASE are not supported.
-
Implemented various security fixes.
v3.0.0
Terraform Provider for Delphix v3.0.0
This release adds the following new features:
None
This release resolves the following bugs:
We have introduced a new required field to the delphix_appdata_dsource resource called source_value. This is meant to resolve an issue where a name specified for the resource's source_id value would be replaced by the id on subsequent runs. This would cause unintended configuration drift and broken repeat apply attempts. The source_id is now an optional value. All configurations of the dSource resource must be updated.
v2.1.0
Terraform Provider for Delphix v2.1.0
This release includes:
- Added support for linking data sources that are managed by the Connector Plugin framework, such as PostgreSQL.
- Oracle, SQL Server, and SAP ASE are not supported.
For more details, refer to DCT's documentation
v2.0.0
Terraform Provider for Delphix v2.0.0
This release includes:
-
Support for many other databases supported by Delphix, including but not limited to PostgreSQL and SAP HANA.
-
Support for Oracle Real Application Clusters (RAC).
-
Support for Transparent Data Encryption (TDE) in Oracle Multitenant databases.
-
Fix where the ‘cluster_node_ids’ parameter was accepting a single object rather than a list.
-
Added support for the ‘API Usage Report’ introduced in DCT v6.0.0. Users can now reference the following key-value pairs when generating the report to understand their usage patterns:
- User-agent: Terraform/ [terraform-version] (+https://www.terraform.io) Terraform-Plugin-SDK/[terraform-plugin-sdk-version] terraform-provider-delphix/[provider-version]
- Client-name: Terraform
This Client Telemetry information is included in all shared support bundles to improve our user experience. For more details, refer to DCT's documentation.
v1.0.1
Terraform Provider for Delphix v1.0.1
Addressed an issue where the terraform plan logic could not handle VDB/Environment drift detection scenarios. Now, if a VDB/Environment is deleted outside of the Terraform workflow, the Delphix provider will recognize and respond accordingly.