You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|[ibm_database_connection.database_connection](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/database_connection)| data source |
86
+
|[ibm_database_point_in_time_recovery.source_db_earliest_pitr_time](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/database_point_in_time_recovery)| data source |
86
87
87
88
### Inputs
88
89
@@ -106,7 +107,7 @@ To attach access management tags to resources in this module, you need the follo
106
107
| <aname="input_name"></a> [name](#input\_name)| The name to give the Postgresql instance. |`string`| n/a | yes |
107
108
| <aname="input_pg_version"></a> [pg\_version](#input\_pg\_version)| Version of the PostgreSQL instance. If no value is passed, the current preferred version of IBM Cloud Databases is used. |`string`|`null`| no |
108
109
| <aname="input_pitr_id"></a> [pitr\_id](#input\_pitr\_id)| (Optional) The ID of the source deployment PostgreSQL instance that you want to recover back to. The PostgreSQL instance is expected to be in an up and in running state. |`string`|`null`| no |
109
-
| <aname="input_pitr_time"></a> [pitr\_time](#input\_pitr\_time)| (Optional) The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deploymentnameorCRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr|`string`|`null`| no |
110
+
| <aname="input_pitr_time"></a> [pitr\_time](#input\_pitr\_time)| (Optional) The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. If empty string ("") is passed, earliest\_point\_in\_time\_recovery\_time will be used as pitr\_time. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deploymentnameorCRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr|`string`|`null`| no |
110
111
| <aname="input_region"></a> [region](#input\_region)| The region where you want to deploy your instance. |`string`|`"us-south"`| no |
111
112
| <aname="input_remote_leader_crn"></a> [remote\_leader\_crn](#input\_remote\_leader\_crn)| A CRN of the leader database to make the replica(read-only) deployment. The leader database is created by a database deployment with the same service ID. A read-only replica is set up to replicate all of your data from the leader deployment to the replica deployment by using asynchronous replication. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-read-only-replicas|`string`|`null`| no |
112
113
| <aname="input_resource_group_id"></a> [resource\_group\_id](#input\_resource\_group\_id)| The resource group ID where the PostgreSQL instance will be created. |`string`| n/a | yes |
@@ -128,6 +129,7 @@ To attach access management tags to resources in this module, you need the follo
Copy file name to clipboardExpand all lines: examples/pitr/variables.tf
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -45,11 +45,16 @@ variable "pitr_id" {
45
45
46
46
variable"pitr_time" {
47
47
type=string
48
-
description="The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. If empty string (\"\") or spaced string (\"\") is passed, latest_point_in_time_recovery_time will be used as pitr_time. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deployment name or CRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr"
48
+
description="The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. If empty string (\"\") is passed, earliest_in_time_recovery_time will be used as pitr_time. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deployment name or CRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr"
49
49
}
50
50
51
51
variable"members" {
52
52
type=number
53
53
description="Allocated number of members. Members must be same or higher than the source deployment PostgreSQL instance."
54
54
default=2
55
55
}
56
+
57
+
variable"member_cpu_count" {
58
+
type=number
59
+
description="Allocated dedicated CPU per member. For shared CPU, set to 0. [Learn more](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling)"
Copy file name to clipboardExpand all lines: variables.tf
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -353,6 +353,6 @@ variable "pitr_id" {
353
353
354
354
variable"pitr_time" {
355
355
type=string
356
-
description="(Optional) The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deployment name or CRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr"
356
+
description="(Optional) The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) for any time in the last 7 days that you want to restore to. If empty string (\"\") is passed, earliest_point_in_time_recovery_time will be used as pitr_time. To retrieve the timestamp, run the command (ibmcloud cdb postgresql earliest-pitr-timestamp <deployment name or CRN>). For more info on Point-in-time Recovery, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-pitr"
0 commit comments