[pre-commit.ci] pre-commit autoupdate

.github/workflows/tfsec.yml

@@ -8,4 +8,4 @@ jobs:
     uses: clouddrove/github-shared-workflows/.github/workflows/tfsec.yml@master
     secrets: inherit
     with:
-      working_directory: '.'
+      working_directory: '.'

.gitignore

@@ -5,4 +5,4 @@
 .idea
 *.iml
 .terraform.tfstate.lock.info
-.terraform.lock.hcl
+.terraform.lock.hcl

.pre-commit-config.yaml

@@ -1,14 +1,14 @@
 repos:
 
   - repo: https://github.com/gruntwork-io/pre-commit
-    rev: v0.1.12 # Get the latest from: https://github.com/gruntwork-io/pre-commit/releases
+    rev: v0.1.23 # Get the latest from: https://github.com/gruntwork-io/pre-commit/releases
     hooks:
       - id: terraform-fmt
       - id: shellcheck
       - id: tflint
 
-  - repo: git://github.com/pre-commit/pre-commit-hooks
-    rev: v4.0.1 # Use the ref you want to point at
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0 # Use the ref you want to point at
     hooks:
       - id: end-of-file-fixer
       - id: trailing-whitespace

README.md

@@ -7,7 +7,7 @@
     Terraform AZURE APP SERVICE
 </h1>
 
-<p align="center" style="font-size: 1.2rem;"> 
+<p align="center" style="font-size: 1.2rem;">
     Terraform module to create app-service resource on AZURE.
      </p>
 
@@ -38,7 +38,7 @@
 <hr>
 
 
-We eat, drink, sleep and most importantly love **DevOps**. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy <b>Bigger problems are always solved by breaking them into smaller manageable problems</b>. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller <b>connected yet manageable pieces</b> within the infrastructure. 
+We eat, drink, sleep and most importantly love **DevOps**. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy <b>Bigger problems are always solved by breaking them into smaller manageable problems</b>. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller <b>connected yet manageable pieces</b> within the infrastructure.
 
 This module is basically combination of [Terraform open source](https://www.terraform.io/) and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
 
@@ -49,7 +49,7 @@ We have [*fifty plus terraform modules*][terraform_modules]. A few of them are c
 
 ## Prerequisites
 
-This module has a few dependencies: 
+This module has a few dependencies:
 
 - [Terraform 1.x.x](https://learn.hashicorp.com/terraform/getting-started/install.html)
 - [Go](https://golang.org/doc/install)
@@ -70,7 +70,7 @@ This module has a few dependencies:
 
 ### Simple Example
 Here is an example of how you can use this module in your inventory structure:
-  #### Default App Service with NODE 
+  #### Default App Service with NODE
 ```hcl
 module "key_vault" {
   source                      = "clouddrove/app-service/azure"
@@ -175,7 +175,7 @@ module "key_vault" {
 
 
 ## Testing
-In this module testing is performed with [terratest](https://github.com/gruntwork-io/terratest) and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a [GO environment](https://golang.org/doc/install) in your system. 
+In this module testing is performed with [terratest](https://github.com/gruntwork-io/terratest) and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a [GO environment](https://golang.org/doc/install) in your system.
 
 You need to run the following command in the testing folder:
 ```hcl
@@ -184,7 +184,7 @@ You need to run the following command in the testing folder:
 
 
 
-## Feedback 
+## Feedback
 If you come accross a bug or have any feedback, please log it in our [issue tracker](https://github.com/clouddrove/terraform-azure-app-service/issues), or feel free to drop us an email at [[email protected]](mailto:[email protected]).
 
 If you have found it worth your time, go ahead and give us a ★ on [our GitHub](https://github.com/clouddrove/terraform-azure-app-service)!

README.yaml

@@ -36,7 +36,7 @@ include:
 usage: |-
   ### Simple Example
   Here is an example of how you can use this module in your inventory structure:
-    #### Default App Service with NODE 
+    #### Default App Service with NODE
   ```hcl
   module "key_vault" {
     source                      = "clouddrove/app-service/azure"

_example/complete/main.tf

@@ -41,4 +41,4 @@ module "app-service" {
   app_settings = {
     WEBSITE_NODE_DEFAULT_VERSION = "~16"
   }
-}
+}

_example/complete/versions.tf

@@ -9,4 +9,4 @@ terraform {
       version = ">=3.0.0"
     }
   }
-}
+}

outputs.tf

@@ -51,4 +51,4 @@ output "source_control" {
 output "site_credential" {
   value       = azurerm_app_service.main[0].site_credential
   description = "A site_credential block as defined below, which contains the site-level credentials used to publish to this App Service."
-}
+}

variables.tf

@@ -249,4 +249,4 @@ variable "integration_subnet_id" {
   type        = string
   default     = null
   description = "The resource ID of the subnet"
-}
+}

versions.tf

@@ -9,4 +9,4 @@ terraform {
       version = ">=3.0.0"
     }
   }
-}
+}