fix: extend the required terraform version to < 1.7 (#145)

Co-authored-by: [email protected] <[email protected]>

Author: akocbek

README.md

@@ -63,7 +63,7 @@ To create service credentials, access to Event Notifications and access to call
 
 | Name | Version |
 |------|---------|
-| <a name="requirement_terraform"></a> [terraform](#requirement\_terraform) | >= 1.3.0, <1.6.0 |
+| <a name="requirement_terraform"></a> [terraform](#requirement\_terraform) | >= 1.3.0, <1.7.0 |
 | <a name="requirement_ibm"></a> [ibm](#requirement\_ibm) | >= 1.56.1, < 2.0.0 |
 | <a name="requirement_time"></a> [time](#requirement\_time) | >= 0.9.1 |
 

common-dev-assets

@@ -1,5 +1,5 @@
 terraform {
-  required_version = ">= 1.3.0, <1.6.0"
+  required_version = ">= 1.3.0, <1.7.0"
 
   # Ensure that there is always 1 example locked into the lowest provider version of the range defined in the main
   # module's version.tf (usually a basic example), and 1 example that will always use the latest provider version.

examples/basic/version.tf

@@ -1,5 +1,5 @@
 terraform {
-  required_version = ">= 1.3.0, <1.6.0"
+  required_version = ">= 1.3.0, <1.7.0"
 
   # Ensure that there is always 1 example locked into the lowest provider version of the range defined in the main
   # module's version.tf (usually a basic example), and 1 example that will always use the latest provider version.

examples/complete/version.tf

@@ -1,5 +1,5 @@
 terraform {
-  required_version = ">= 1.3.0, <1.6.0"
+  required_version = ">= 1.3.0, <1.7.0"
 
   # Use a flexible range in modules that future proofs the module's usage with upcoming minor and patch versions
   required_providers {