Skip to content
This repository was archived by the owner on Jun 17, 2025. It is now read-only.

Commit 2875bde

Browse files
feat: remove plan validation argument (#103)
1 parent d0cdb0c commit 2875bde

File tree

3 files changed

+0
-8
lines changed

3 files changed

+0
-8
lines changed

README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,6 @@ To attach access management tags to resources in this module, you need the follo
100100
| <a name="input_name"></a> [name](#input\_name) | The name given to the Enterprise DB instance. | `string` | n/a | yes |
101101
| <a name="input_pitr_id"></a> [pitr\_id](#input\_pitr\_id) | (Optional) The ID of the source deployment EDB instance that you want to recover back to. The EDB instance is expected to be in an up and in running state. | `string` | `null` | no |
102102
| <a name="input_pitr_time"></a> [pitr\_time](#input\_pitr\_time) | (Optional) The timestamp in UTC format (%Y-%m-%dT%H:%M:%SZ) 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-enterprisedb?topic=databases-for-enterprisedb-pitr | `string` | `null` | no |
103-
| <a name="input_plan_validation"></a> [plan\_validation](#input\_plan\_validation) | Enable or disable validating the database parameters for Enterprise DB during the plan phase. | `bool` | `true` | no |
104103
| <a name="input_region"></a> [region](#input\_region) | The region where you want to deploy your instance. | `string` | `"us-south"` | no |
105104
| <a name="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-enterprisedb?topic=databases-for-enterprisedb-read-only-replicas | `string` | `null` | no |
106105
| <a name="input_resource_group_id"></a> [resource\_group\_id](#input\_resource\_group\_id) | The resource group ID where Enterprise DB instance will be created. | `string` | n/a | yes |

main.tf

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,6 @@ resource "ibm_database" "enterprise_db" {
5757
location = var.region
5858
plan = "standard" # Only standard plan is available for edb
5959
backup_id = var.backup_crn
60-
plan_validation = var.plan_validation
6160
remote_leader_id = var.remote_leader_crn
6261
version = var.edb_version
6362
tags = var.resource_tags

variables.tf

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,6 @@ variable "name" {
1212
description = "The name given to the Enterprise DB instance."
1313
}
1414

15-
variable "plan_validation" {
16-
type = bool
17-
description = "Enable or disable validating the database parameters for Enterprise DB during the plan phase."
18-
default = true
19-
}
20-
2115
variable "remote_leader_crn" {
2216
type = string
2317
description = "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-enterprisedb?topic=databases-for-enterprisedb-read-only-replicas"

0 commit comments

Comments
 (0)