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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -101,10 +101,10 @@ To attach access management tags to resources in this module, you need the follo
101
101
| <aname="input_member_cpu_count"></a> [member\_cpu\_count](#input\_member\_cpu\_count)| Allocated dedicated CPU per member. For shared CPU, set to 0. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling|`number`|`0`| no |
102
102
| <aname="input_member_disk_mb"></a> [member\_disk\_mb](#input\_member\_disk\_mb)| Allocated disk per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling|`number`|`5120`| no |
103
103
| <aname="input_member_host_flavor"></a> [member\_host\_flavor](#input\_member\_host\_flavor)| Allocated host flavor per member. For more information, see https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database#host_flavor|`string`|`null`| no |
104
-
| <aname="input_member_memory_mb"></a> [member\_memory\_mb](#input\_member\_memory\_mb)| Allocated memory per-member. See the following doc for supported values:https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling|`number`|`4096`| no |
104
+
| <aname="input_member_memory_mb"></a> [member\_memory\_mb](#input\_member\_memory\_mb)| Allocated memory permember. For more information, seehttps://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling|`number`|`4096`| no |
105
105
| <aname="input_members"></a> [members](#input\_members)| Allocated number of members. Members can be scaled up but not down. |`number`|`2`| no |
106
106
| <aname="input_name"></a> [name](#input\_name)| The name to give the Postgresql instance. |`string`| n/a | yes |
107
-
| <aname="input_pg_version"></a> [pg\_version](#input\_pg\_version)| Version of the PostgreSQL instance to provision. If no value is passed, the current preferred version of IBM Cloud Databases is used. |`string`|`null`| no |
107
+
| <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
108
| <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
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
110
| <aname="input_region"></a> [region](#input\_region)| The region where you want to deploy your instance. |`string`|`"us-south"`| no |
Copy file name to clipboardExpand all lines: modules/fscloud/variables.tf
+54-90Lines changed: 54 additions & 90 deletions
Original file line number
Diff line number
Diff line change
@@ -12,11 +12,6 @@ variable "name" {
12
12
description="The name to give the Postgresql instance."
13
13
}
14
14
15
-
variable"existing_kms_instance_guid" {
16
-
description="The GUID of the Hyper Protect Crypto Services instance."
17
-
type=string
18
-
}
19
-
20
15
variable"pg_version" {
21
16
description="Version of the PostgreSQL instance. If no value is passed, the current preferred version of IBM Cloud Databases is used."
22
17
type=string
@@ -29,16 +24,13 @@ variable "region" {
29
24
default="us-south"
30
25
}
31
26
32
-
variable"member_memory_mb" {
33
-
type=number
34
-
description="Allocated memory per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
description="Allocated disk per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
41
-
default=5120
32
+
description="Allocated number of members. Members can be scaled up but not down."
33
+
default=2
42
34
}
43
35
44
36
variable"member_cpu_count" {
@@ -47,12 +39,24 @@ variable "member_cpu_count" {
47
39
default=3
48
40
}
49
41
42
+
variable"member_disk_mb" {
43
+
type=number
44
+
description="Allocated disk per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
45
+
default=5120
46
+
}
47
+
50
48
variable"member_host_flavor" {
51
49
type=string
52
50
description="Allocated host flavor per member. For more information, see https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/database#host_flavor"
53
51
default=null
54
52
}
55
53
54
+
variable"member_memory_mb" {
55
+
type=number
56
+
description="Allocated memory per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
57
+
default=4096
58
+
}
59
+
56
60
variable"admin_pass" {
57
61
type=string
58
62
description="The password for the database administrator. If the admin password is null then the admin user ID cannot be accessed. More users can be specified in a user block."
error_message="Value for `configuration[\"max_wal_senders\"]` must be 12 or more, if specified."
178
-
}
179
126
}
180
127
181
-
variable"kms_key_crn" {
182
-
type=string
183
-
description="The root key CRN of the Hyper Protect Crypto Service (HPCS) to use for disk encryption."
184
-
}
185
-
186
-
variable"backup_encryption_key_crn" {
187
-
type=string
188
-
description="The CRN of a Hyper Protect Crypto Service use for encrypting the disk that holds deployment backups. Only used if var.kms_encryption_enabled is set to true. There are limitation per region on the Hyper Protect Crypto Services and region for those services. See https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hpcs#use-hpcs-backups"
189
-
default=null
190
-
# Validation happens in the root module
191
-
}
192
-
193
-
variable"skip_iam_authorization_policy" {
194
-
type=bool
195
-
description="Set to true to skip the creation of an IAM authorization policy that permits all PostgreSQL database instances in the resource group to read the encryption key from the Hyper Protect Crypto Services instance. The HPCS instance is passed in through the var.existing_kms_instance_guid variable."
description="The CRN of a backup resource to restore from. The backup is created by a database deployment with the same service ID. The backup is loaded after provisioning and the new deployment starts up that uses that data. A backup CRN is in the format crn:v1:<…>:backup:. If omitted, the database is provisioned empty."
165
+
description="The root key CRN of the Hyper Protect Crypto Service (HPCS) to use for disk encryption."
166
+
}
167
+
168
+
variable"backup_encryption_key_crn" {
169
+
type=string
170
+
description="The CRN of a Hyper Protect Crypto Service use for encrypting the disk that holds deployment backups. Only used if var.kms_encryption_enabled is set to true. There are limitation per region on the Hyper Protect Crypto Services and region for those services. See https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-hpcs#use-hpcs-backups"
229
171
default=null
172
+
# Validation happens in the root module
173
+
}
174
+
175
+
variable"skip_iam_authorization_policy" {
176
+
type=bool
177
+
description="Set to true to skip the creation of an IAM authorization policy that permits all PostgreSQL database instances in the resource group to read the encryption key from the Hyper Protect Crypto Services instance. The HPCS instance is passed in through the var.existing_kms_instance_guid variable."
178
+
default=false
179
+
}
180
+
181
+
variable"existing_kms_instance_guid" {
182
+
description="The GUID of the Hyper Protect Crypto Services instance."
description="The CRN of a backup resource to restore from. The backup is created by a database deployment with the same service ID. The backup is loaded after provisioning and the new deployment starts up that uses that data. A backup CRN is in the format crn:v1:<…>:backup:. If omitted, the database is provisioned empty."
description="Allocated memory per-member. See the following doc for supported values: https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
46
-
default=4096
48
+
description="Allocated number of members. Members can be scaled up but not down."
49
+
default=2
47
50
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
48
51
}
49
52
50
-
variable"member_disk_mb" {
53
+
variable"member_cpu_count" {
51
54
type=number
52
-
description="Allocated disk per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
53
-
default=5120
55
+
description="Allocated dedicated CPU per member. For shared CPU, set to 0. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
56
+
default=0
54
57
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
55
58
}
56
59
57
-
variable"member_cpu_count" {
60
+
variable"member_disk_mb" {
58
61
type=number
59
-
description="Allocated dedicated CPU per member. For shared CPU, set to 0. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
60
-
default=0
62
+
description="Allocated disk per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
63
+
default=5120
61
64
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
69
72
}
70
73
74
+
variable"member_memory_mb" {
75
+
type=number
76
+
description="Allocated memory per member. For more information, see https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-resources-scaling"
77
+
default=4096
78
+
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
79
+
}
80
+
81
+
variable"admin_pass" {
82
+
type=string
83
+
description="The password for the database administrator. If the admin password is null then the admin user ID cannot be accessed. More users can be specified in a user block."
84
+
default=null
85
+
sensitive=true
86
+
}
87
+
88
+
variable"users" {
89
+
type=list(object({
90
+
name =string
91
+
password =string# pragma: allowlist secret
92
+
type =string# "type" is required to generate the connection string for the outputs.
93
+
role =optional(string)
94
+
}))
95
+
default=[]
96
+
sensitive=true
97
+
description="A list of users that you want to create on the database. Multiple blocks are allowed. The user password must be in the range of 10-32 characters. Be warned that in most case using IAM service credentials (via the var.service_credential_names) is sufficient to control access to the Postgres instance. This blocks creates native postgres database users, more info on that can be found here https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-user-management&interface=ui"
98
+
}
99
+
71
100
variable"service_credential_names" {
72
101
description="Map of name, role for service credentials that you want to create for the database"
description="Allocated number of members. Members can be scaled up but not down."
85
-
default=2
86
-
# Validation is done in the Terraform plan phase by the IBM provider, so no need to add extra validation here.
87
-
}
88
-
89
111
variable"service_endpoints" {
90
112
type=string
91
113
description="Specify whether you want to enable the public, private, or both service endpoints. Supported values are 'public', 'private', or 'public-and-private'."
@@ -192,25 +214,6 @@ variable "configuration" {
192
214
}
193
215
}
194
216
195
-
variable"admin_pass" {
196
-
type=string
197
-
description="The password for the database administrator. If the admin password is null then the admin user ID cannot be accessed. More users can be specified in a user block."
198
-
default=null
199
-
sensitive=true
200
-
}
201
-
202
-
variable"users" {
203
-
type=list(object({
204
-
name =string
205
-
password =string# pragma: allowlist secret
206
-
type =string# "type" is required to generate the connection string for the outputs.
207
-
role =optional(string)
208
-
}))
209
-
default=[]
210
-
sensitive=true
211
-
description="A list of users that you want to create on the database. Multiple blocks are allowed. The user password must be in the range of 10-32 characters. Be warned that in most case using IAM service credentials (via the var.service_credential_names) is sufficient to control access to the Postgres instance. This blocks creates native postgres database users, more info on that can be found here https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-user-management&interface=ui"
0 commit comments