Skip to content

Commit 952fea8

Browse files
Uddipaan-HazarikaUddipaan-Hazarika
authored
Merge pull request #108 from Uddipaan-Hazarika/dsource_update
DLPXECO-5238 | Oracle Dsource update support for UIP and drift detection
2 parents 8694d67 + d384cb4 commit 952fea8

File tree

25 files changed

+1023
-467
lines changed

25 files changed

+1023
-467
lines changed

‎.goreleaser.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# Visit https://goreleaser.com for documentation on how to customize this
22
# behavior.
33
env:
4-
- PROVIDER_VERSION=3.3.2
4+
- PROVIDER_VERSION=3.4.0
55
before:
66
hooks:
77
# this is just an example and not a requirement for provider building/publishing

‎.whitesource

Lines changed: 45 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,48 @@
11
{
2-
"scanSettings": {
3-
"configMode": "AUTO",
4-
"configExternalURL": "",
5-
"projectToken": "",
6-
"baseBranches": []
7-
},
8-
"scanSettingsSAST": {
9-
"enableScan": true,
10-
"scanPullRequests": true,
11-
"incrementalScan": true,
12-
"baseBranches": [],
13-
"snippetSize": 10
14-
},
15-
"checkRunSettings": {
16-
"vulnerableCheckRunConclusionLevel": "failure",
17-
"displayMode": "diff",
18-
"useMendCheckNames": true
19-
},
20-
"checkRunSettingsSAST": {
21-
"checkRunConclusionLevel": "failure",
22-
"severityThreshold": "high"
23-
},
24-
"issueSettings": {
25-
"minSeverityLevel": "LOW",
26-
"issueType": "DEPENDENCY"
27-
},
28-
"issueSettingsSAST": {
29-
"minSeverityLevel": "high",
30-
"issueType": "repo"
31-
},
32-
"remediateSettings": {
33-
"workflowRules": {
34-
"enabled": true
2+
"scanSettings": {
3+
"configMode": "AUTO",
4+
"configExternalURL": "",
5+
"projectToken": "",
6+
"enableLicenseViolations": "true",
7+
"displayLicenseViolations": "true",
8+
"enableIaC": "true",
9+
"baseBranches": []
10+
},
11+
"scanSettingsSAST": {
12+
"enableScan": true,
13+
"scanPullRequests": true,
14+
"incrementalScan": true,
15+
"baseBranches": [],
16+
"snippetSize": 10
17+
},
18+
"checkRunSettings": {
19+
"vulnerableCheckRunConclusionLevel": "failure",
20+
"displayMode": "diff",
21+
"useMendCheckNames": true
22+
},
23+
"checkRunSettingsSAST": {
24+
"checkRunConclusionLevel": "failure",
25+
"severityThreshold": "high"
26+
},
27+
"issueSettings": {
28+
"minSeverityLevel": "LOW",
29+
"issueType": "DEPENDENCY"
30+
},
31+
"issueSettingsSAST": {
32+
"minSeverityLevel": "high",
33+
"issueType": "repo"
34+
},
35+
"remediateSettings": {
36+
"workflowRules": {
37+
"enabled": true
38+
}
39+
},
40+
"imageSettings":{
41+
"imageTracing":{
42+
"enableImageTracingPR": false,
43+
"addRepositoryCoordinate": false,
44+
"addDockerfilePath": false,
45+
"addMendIdentifier": false
46+
}
3547
}
36-
},
37-
"imageSettings":{
38-
"imageTracing":{
39-
"enableImageTracingPR": false,
40-
"addRepositoryCoordinate": false,
41-
"addDockerfilePath": false,
42-
"addMendIdentifier": false
43-
}
44-
}
4548
}

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
Terraform Provider for Delphix enables Terraform to create and manage Delphix Continuous Data &
88
Continuous Compliance infrastructure using the Delphix Control Tower (DCT) APIs.
99

10-
Full implementation directions can be found on the [Delphix Ecosystem Documentation](https://ecosystem.delphix.com/docs/overview-3) and [Terraform Provider Registry](https://registry.terraform.io/providers/delphix-integrations/delphix/latest/docs).
10+
Full implementation directions can be found on the [Delphix Ecosystem Documentation](https://help.delphix.com/eh/current/Content/Ecoystem/Terraform.htm) and [Terraform Provider Registry](https://registry.terraform.io/providers/delphix-integrations/delphix/latest/docs).
1111

1212
## Prerequisites
1313

‎docs/index.md

Lines changed: 82 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -1,80 +1,82 @@
1-
# <provider> Delphix Provider
2-
3-
The Terraform Provider for Delphix enables you to natively manage data-as-code along with your infrastructure.
4-
5-
With Terraform and Delphix, you can now automatically provision, manage, and teardown any number of ephemeral data environments to drive enterprise DevOps workflows, such as test data management.
6-
7-
This provider communicates directly with Data Control Tower (DCT) to generated virtual database and other objects. Therefore, DCT must be registered with one or more Delphix Continuous Data Engines.
8-
9-
To learn more about Delphix and DCT APIs, refer to [Delphix Documentation](https://documentation.delphix.com/docs/) and [DCT Documentation](https://dct.delphix.com/docs/latest/) respectively. Please [Contact us](ask-integrations@delphix.com) (ask-integrations@delphix.com) with any questions.
10-
11-
If you are entitled to Data Control Tower then you may also send support issues through the [Delphix Support Portal](https://support.delphix.com/).
12-
13-
## System Requirements
14-
15-
| Product | Version |
16-
|--------------------------------|----------|
17-
| Data Control Tower (DCT) | v22+ |
18-
| Delphix Continuous Data Engine | v16.0.0.0+ |
19-
20-
Note: The DCT version above guarantees full provider support. However, each resource might support older versions. Refer to the specific resource documentation page for more information.
21-
22-
## Release Notes
23-
24-
The Delphix Provider's complete release notes can be found in the [Delphix Ecosystem Documentation](https://ecosystem.delphix.com/docs/main/release-notes-terraform).
25-
26-
## Connectivity and Authentication
27-
28-
All communication is performed through HTTPS. The Delphix Provider uses Data Control Tower (DCT) APIs to communicate with Delphix Continuous Data Engines.
29-
30-
Authentication with DCT APIs are managed using API Keys. For generation of an API key, please refer to [DCT API Keys](https://dct.delphix.com/docs/latest/api-keys).
31-
32-
## Example Usage
33-
34-
The following script demonstrates how to configure the Delphix Provider to connect with Data Control Tower and then provision a VDB. Additional resource guides and documentation can be found on the left hand side.
35-
36-
```hcl
37-
terraform {
38-
required_providers {
39-
delphix = {
40-
source = "delphix-integrations/delphix"
41-
version = "3.3.0"
42-
}
43-
}
44-
}
45-
46-
# Configure the DXI Provider
47-
provider "delphix" {
48-
host = "dct_hostname"
49-
key = "dct_api_key"
50-
tls_insecure_skip = false
51-
}
52-
53-
# Provision a VDB
54-
resource "delphix_vdb" "vdb_name" {
55-
auto_select_repository = true
56-
source_data_id = "DATASOURCE_ID"
57-
}
58-
```
59-
60-
### Example Global Parameter Reference
61-
62-
* __host__: The hostname for DCT.
63-
* __key__ : The API Key which is used to authenticate with DCT. (Example `apk 2.abc123...`).
64-
* __tls_insecure_skip__: (Optional) A boolean value which determines whether to skip the SSL/TLS check. The default value is `false`. Skipping any SSL/TLS check is not recommended for production environments.
65-
* __host_scheme__: (Optional) Determines the configured host URL's scheme. The default value is `https`.
66-
67-
Consult the documentation's Resources section for details on individual resources, such as VDB, dSource, and Environment.
68-
69-
## Support Matrix
70-
71-
Feature/Product | Provider Version | DCT version
72-
--- |------------------| --- |
73-
delphix_vdb | v 1.0.0 | v 2.0.0
74-
delphix_vdb_group | v 1.0.0 | v 2.0.0
75-
delphix_environment | v 1.0.0 | v 2.0.0
76-
delphix_appdata_dsource | v 2.1.0 | v 10.0.0
77-
delphix_oracle_dsource | v 3.1.0 | v 10.0.0
78-
delphix_database_postgresql | v 3.2.0 | v 14.0.0
79-
delphix_vdb update<br>delphix_database_postgresql import | v 3.3.0 | v 22.0.0
80-
1+
# <provider> Delphix Provider
2+
3+
The [Terraform Provider for Delphix](https://help.delphix.com/eh/current/content/terraform.htm) enables you to natively manage data-as-code along with your infrastructure.
4+
5+
With Terraform and Delphix, you can now automatically provision, manage, and teardown any number of ephemeral data environments to drive enterprise DevOps workflows, such as test data management.
6+
7+
The Delphix provider communicates directly with Data Control Tower (DCT) to generated virtual database and other objects. Therefore, DCT must be registered with one or more Delphix Continuous Data Engines.
8+
9+
To learn more about Delphix and DCT APIs, refer to [Delphix Documentation](https://documentation.delphix.com/docs/) and [DCT Documentation](https://dct.delphix.com/docs/latest/). Please [submit a GitHub issue](https://github.com/delphix-integrations/terraform-provider-delphix/issues) if you have any questions.
10+
11+
If you are a DCT customer, you can also request support from the [Delphix Support Portal](https://support.delphix.com/).
12+
13+
## System Requirements
14+
15+
| Product | Version |
16+
|--------------------------------|----------|
17+
| Data Control Tower (DCT) | v2025.1.2+ |
18+
| Delphix Continuous Data Engine | v29.0.0.0+ |
19+
20+
Note: The DCT and Continuous Data versions above guarantees full provider support. However, each resource might support older versions. Refer to the specific resource documentation page for more information.
21+
22+
## Release Notes
23+
24+
The Delphix Provider's release notes can be found in the [Delphix Ecosystem Documentation](https://help.delphix.com/eh/current/Content/Ecoystem/Release_notes__Terraform_.htm).
25+
26+
## Connectivity and Authentication
27+
28+
All communication is performed through HTTPS. The Delphix Provider uses DCT APIs to communicate with Delphix Continuous Data Engines.
29+
30+
Authentication with DCT APIs is managed using API Keys. For generation of an API key, please refer to [DCT API Keys](https://dct.delphix.com/docs/latest/api-keys). For example: `apk 2.12345...`
31+
32+
## Example Usage
33+
34+
The following script demonstrates how to configure the Delphix Provider to connect with Data Control Tower and then provision a VDB. Additional resource guides and documentation can be found on the left-hand side.
35+
36+
```hcl
37+
38+
# Install the Delphix Provider
39+
terraform {
40+
required_providers {
41+
delphix = {
42+
source = "delphix-integrations/delphix"
43+
version = "3.4.0"
44+
}
45+
}
46+
}
47+
48+
# Connect the Delphix Provider to DCT
49+
provider "delphix" {
50+
host = "<insert_dct_hostname>"
51+
key = "<insert_dct_api_key>"
52+
tls_insecure_skip = false
53+
}
54+
55+
# Provision a VDB with the latest snapshot of data source
56+
resource "delphix_vdb" "vdb_name" {
57+
auto_select_repository = true
58+
source_data_id = "<insert datasource_id>"
59+
}
60+
```
61+
62+
### Example Global Parameter Reference
63+
64+
* __host__: The hostname for DCT.
65+
* __key__: The API Key which is used to authenticate with DCT. (Example `apk 2.abc123...`).
66+
* __tls_insecure_skip__: (Optional) A boolean value which determines whether to skip the SSL/TLS check. The default value is `false`. Skipping any SSL/TLS check is not recommended for production environments.
67+
* __host_scheme__: (Optional) Determines the configured host URL's scheme. The default value is `https`.
68+
69+
Consult the Resources section for details on individual resources, such as VDB, dSource, and Environment.
70+
71+
## Support Matrix
72+
73+
| Feature | Provider Version | DCT Version |
74+
|---------------------------------------------|------------------|-------------|
75+
| delphix_vdb | v 1.0.0 | v 2.0.0 |
76+
| delphix_vdb_group | v 1.0.0 | v 2.0.0 |
77+
| delphix_environment | v 1.0.0 | v 2.0.0 |
78+
| delphix_appdata_dsource | v 2.1.0 | v 10.0.0 |
79+
| delphix_oracle_dsource | v 3.1.0 | v 10.0.0 |
80+
| delphix_database_postgresql | v 3.2.0 | v 14.0.0 |
81+
| delphix_vdb update<br>delphix_database_postgresql import | v 3.3.0 | v 22.0.0 |
82+
| delphix_oracle_dsource update<br>delphix_oracle_dsource import | v 3.4.0 | v 2025.1.2 |

‎docs/resources/appdata_dsource.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -125,6 +125,8 @@ resource "delphix_appdata_dsource" "dsource_name" {
125125

126126
* `make_current_account_owner` - (Required) Whether the account creating this reporting schedule must be configured as owner of the reporting schedule.
127127

128+
* `rollback_on_failure` - Dsource linking operation when fails during snapsync creates a tainted dsource on the engine. Setting this flag to true will remove the tainted dsource from state as well as engine. By default, it is set to false, where the tainted dsource is maintained on the terraform state.
129+
128130
* `description` - The notes/description for the dSource.
129131

130132
* `link_type` - (Required) The type of link to create. Default is AppDataDirect.
@@ -187,6 +189,6 @@ resource "delphix_appdata_dsource" "dsource_name" {
187189

188190
* `sync_parameters` - The JSON payload conforming to the snapshot parameters definition in a LUA toolkit or platform plugin.
189191

190-
* `skip_wait_for_snapshot_creation` - By default this resource will wait for a snapshot to be created post-dSource creation. This ensure a snapshot is available during the VDB provisioning. This behavior can be skipped by setting this parameter to `true`.
192+
* `skip_wait_for_snapshot_creation` - In DCT v2025.1, waiting for Ingestion and Snapshotting (aka SnapSync) to complete is default functionality. Therefore, these the arguments skip_wait_for_snapshot_creation and wait_time are ignored. In future versions of the provider, we will look at re-implementing the skip SnapSync behavior
191193

192-
* `wait_time` - By default this resource waits 0 minutes for a snapshot to be created. Increase the integer value as needed for larger dSource snapshots. This parameter can be ignored if 'skip_wait_for_snapshot_creation' is set to `true`.
194+
* `wait_time` - In DCT v2025.1, waiting for Ingestion and Snapshotting (aka SnapSync) to complete is default functionality. Therefore, these the arguments skip_wait_for_snapshot_creation and wait_time are ignored. In future versions of the provider, we will look at re-implementing the skip SnapSync behavior.

0 commit comments

Comments
 (0)