fix: updates to mod template (#594)

README.md

@@ -24,6 +24,8 @@ The default structure includes the following files:
 - `version.tf`: The required terraform and provider versions
 - `variables.tf`: The input variables for the module
 - `outputs.tf`: The values that are output from the module
+
+Use nested modules to split complex behavior into smaller modules that advanced users can choose from. Put nested modules under a `/modules` subdirectory. If you include more than one nested module, make the submodules [composable](https://developer.hashicorp.com/terraform/language/modules/develop/composition) by the caller. In other words, don't embed calls between submodules to create a deeply nested tree of modules.
 For more information, see [Module structure](https://terraform-ibm-modules.github.io/documentation/#/module-structure) in the project documentation.
 
 You can add other content to support what your module does and how it works. For example, you might add a `scripts/` directory that contains shell scripts that are run by a `local-exec` `null_resource` in the Terraform module.
@@ -146,7 +148,7 @@ statement instead the previous block.
 
 | Name | Version |
 |------|---------|
-| <a name="requirement_terraform"></a> [terraform](#requirement\_terraform) | >= 1.3, < 1.6 |
+| <a name="requirement_terraform"></a> [terraform](#requirement\_terraform) | >= 1.3.0 |
 
 ## Modules
 

examples/basic/version.tf

@@ -1,6 +1,5 @@
 terraform {
-  # Since hashicorp can include breaking changes in minor version updates, ensure to lock into a range here.
-  required_version = ">= 1.3, < 1.6"
+  required_version = ">= 1.3.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,6 +1,5 @@
 terraform {
-  # Since hashicorp can include breaking changes in minor version updates, ensure to lock into a range here.
-  required_version = ">= 1.3, < 1.6"
+  required_version = ">= 1.3.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.

module-metadata.json

@@ -3,7 +3,7 @@
   "variables": {},
   "outputs": {},
   "required_core": [
-    "\u003e= 1.3, \u003c 1.6"
+    "\u003e= 1.3.0"
   ],
   "required_providers": {},
   "managed_resources": {},

version.tf

@@ -1,6 +1,5 @@
 terraform {
-  # Since hashicorp can include breaking changes in minor version updates, ensure to lock into a range here.
-  required_version = ">= 1.3, < 1.6"
+  required_version = ">= 1.3.0"
 
   # Use a flexible range in modules that future proofs the module's usage with upcoming minor and patch versions
   #  required_providers {