Skip to content

Commit 5b50e7d

Browse files
updated md files
1 parent 542dfc0 commit 5b50e7d

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

docs/resources/appdata_dsource.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,9 @@ The Appdata dSource resource allows Terraform to create and delete AppData dSour
1313
## Upgrade Guide
1414
* Any new dSource created post Version>=3.2.1 can set `wait_time` to wait for snapshot creation , dSources created prior to this version will not support this capability
1515

16+
## Note
17+
* `status` and `enabled` are subject to change in the state file based on the dSource state.
18+
1619
## Example Usage
1720

1821
The linking of a dSource can be configured through various ingestion approaches. Each configuration is customized to the connector and its supported options. The three PostgreSQL parameter sets below show working examples.

docs/resources/oracle_dsource.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,12 @@ The Oracle dSource resource allows Terraform to create and delete Oracle dSource
1010
* Data Control Tower v10.0.1+ is required for dSource management. Lower versions are not supported.
1111
* This Oracle dSource Resource only supports Oracle. See the AppData dSource Resource for the support of other connectors (i.e. AppData), such as PostgreSQL and SAP HANA. The Delphix Provider does not support SQL Server or SAP ASE.
1212

13+
## Upgrade Guide
14+
* Any new dSource created post Version>=3.2.1 can set `wait_time` to wait for snapshot creation , dSources created prior to this version will not support this capability
15+
16+
## Note
17+
* `status` and `enabled` are subject to change in the state file based on the dSource state.
18+
1319
## Example Usage
1420

1521
* The linking of a dSource can be performed via direct ingestion as shown in the example below

0 commit comments

Comments
 (0)