New phpIPAM serverless third parties solution in blueprints

blueprints/data-solutions/cloudsql-multiregion/README.md

@@ -179,5 +179,5 @@ module "test" {
   }
   prefix = "prefix"
 }
-# tftest modules=9 resources=43
+# tftest modules=9 resources=44
 ```

blueprints/data-solutions/composer-2/README.md

@@ -139,5 +139,5 @@ module "test" {
   }
   prefix = "prefix"
 }
-# tftest modules=5 resources=28
+# tftest modules=5 resources=29
 ```

blueprints/serverless/cloud-run-explore/README.md

@@ -214,5 +214,5 @@ module "test" {
   }
 }
 
-# tftest modules=4 resources=18
+# tftest modules=4 resources=19
 ```

blueprints/third-party-solutions/README.md

@@ -6,12 +6,18 @@ The blueprints in this folder show how to automate installation of specific thir
 
 ### OpenShift cluster bootstrap on Shared VPC
 
-<a href="./openshift/" title="HubOpenShift bootstrap example"><img src="./openshift/diagram.png" align="left" width="280px"></a> This [example](./openshift/) shows how to quickly bootstrap an OpenShift 4.7 cluster on GCP, using typical enterprise features like Shared VPC and CMEK for instance disks.
+<a href="./openshift/" title="HubOpenShift bootstrap example"><img src="./openshift/diagram.png" align="left" width="320px"></a> <p style="margin-left: 340px"> This [example](./openshift/) shows how to quickly bootstrap an OpenShift 4.7 cluster on GCP, using typical enterprise features like Shared VPC and CMEK for instance disks. </p>
 
 <br clear="left">
 
 ### Wordpress deployment on Cloud Run
 
-<a href="./wordpress/cloudrun/" title="Wordpress deployment on Cloud Run"><img src="./wordpress/cloudrun/architecture.png" align="left" width="280px"></a> This [example](./wordpress/cloudrun/) shows how to deploy a functioning new Wordpress website exposed to the public internet via CloudRun and Cloud SQL, with minimal technical overhead.
+<a href="./wordpress/cloudrun/" title="Wordpress deployment on Cloud Run"><img src="./wordpress/cloudrun/images/architecture.png" align="left" width="320px"></a> <p style="margin-left: 340px"> This [example](./wordpress/cloudrun/) shows how to deploy a functioning new Wordpress website exposed to the public internet via CloudRun and Cloud SQL, with minimal technical overhead. </p>
 
 <br clear="left">
+
+### Serverless phpIPAM on Cloud Run
+
+<a href="./phpipam/" title="phpIPAM bootstrap example"><img src="./phpipam/images/phpipam.png" align="left" width="320px"></a> <p style="margin-left: 340px">This [example](./phpipam/) shows how to quickly bootstrap a serverless phpIPAM instance on GCP using Cloud Run. This comes with typical enterprise features like Shared VPC, Cloud Armor with IAP and, possibly, private exposure via Internal Application Load Balancer. Indeed, the script supports deploying the application either publicly via Global Application Load Balancer with restricted access based on IPs (Cloud Armor) and identities (Identity Aware Proxy) or privately via Internal Application Load Balancer.</p>
+
+<br clear="left">

blueprints/third-party-solutions/phpipam/README.md

@@ -0,0 +1,239 @@
+# Serverless phpIPAM on Cloud Run
+
+[phpIPAM](https://phpipam.net/) is an open-source IP address management (IPAM)
+system that can be used to manage IP addresses in both on-premises and cloud
+environments. It is a powerful tool that can help businesses to automate IP
+address management, proactively identify and resolve IP address conflicts, and
+plan for future IP address needs.
+
+This repository aims to speed up deployment of phpIPAM software on Google Cloud
+Platform Cloud Run serverless product. The web application can be exposed either
+publicly via Global Application Load Balancer or internally via Internal
+Application Load Balancer. More information on the architecture section.
+
+## Architecture
+
+![Serverless phpIPAM on Cloud Run](images/phpipam.png "Wordpress on Cloud Run")
+
+The main components that are deployed in this architecture are the following (
+you can learn about them by following the hyperlinks):
+
+- [Cloud Run](https://cloud.google.com/run): serverless PaaS offering to host
+  containers for web-oriented applications, while offering security, scalability
+  and easy versioning
+- [Cloud SQL](https://cloud.google.com/sql): Managed solution for SQL databases
+- [VPC Serverless Connector](https://cloud.google.com/vpc/docs/serverless-vpc-access):
+  Solution to access the CloudSQL VPC from Cloud Run, using only internal IP
+  addresses
+- [Global Application Load Balancer](https://cloud.google.com/load-balancing/docs/https) (\*):
+  An external Application Load Balancer is a proxy-based Layer 7 load balancer
+  that enables you to run and scale your services behind a single external IP
+  address.
+- [Cloud Armor](https://cloud.google.com/armor/docs/cloud-armor-overview) (\*):
+  Help protect your applications and websites against denial of service and web
+  attacks.
+- [Identity Aware Proxy](https://cloud.google.com/iap/docs/concepts-overview) (\*):
+  IAP lets you establish a central authorization layer for applications accessed
+  by HTTPS, so you can use an application-level access control model instead of
+  relying on network-level firewalls.
+- [Regional Internal Application Load Balancer](https://cloud.google.com/load-balancing/docs/l7-internal) (\*):
+  A Google Cloud internal Application Load Balancer is a regional proxy-based
+  layer 7 load balancer that enables you expose your services behind a single
+  internal IP address.
+
+> (\*) Product deployment depends on input variables
+
+## Setup
+
+### Prerequisites
+
+#### Setting up the project for the deployment
+
+This example will deploy all its resources into the project defined by
+the `project_id` variable. Please note that we assume this project already
+exists. However, if you provide the appropriate values to the `project_create`
+variable, the project will be created as part of the deployment.
+
+If `project_create` is left to null, the identity performing the deployment
+needs the `owner` role on the project defined by the `project_id` variable.
+Otherwise, the identity performing the deployment
+needs `resourcemanager.projectCreator` on the resource hierarchy node specified
+by `project_create.parent` and `billing.user` on the billing account specified
+by `project_create.billing_account_id`.
+
+### Deployment
+
+#### Step 0: Cloning the repository
+
+If you want to deploy from your Cloud Shell, click on the image below, sign in
+if required and when the prompt appears, click on “confirm”.
+
+[![Open Cloudshell](../../../assets/images/cloud-shell-button.png)](https://shell.cloud.google.com/cloudshell/editor?cloudshell_git_repo=https%3A%2F%2Fgithub.com%2FGoogleCloudPlatform%2Fcloud-foundation-fabric&cloudshell_workspace=blueprints%2Fthird-party-solutions%2Fwordpress%2Fcloudrun)
+
+Otherwise, in your console of choice:
+
+```bash
+git clone https://github.com/GoogleCloudPlatform/cloud-foundation-fabric
+```
+
+Before you deploy the architecture, you will need at least the following
+information (for more precise configuration see the Variables section):
+
+* The project ID.
+
+#### Step 2: Prepare the variables
+
+Once you have the required information, head back to your cloned repository.
+Make sure you’re in the directory of this tutorial (where this README is in).
+
+Configure the Terraform variables in your `terraform.tfvars` file.
+See [terraform.tfvars.sample](terraform.tfvars.sample) as starting point - just
+copy it to `terraform.tfvars` and edit the latter. See the variables
+documentation below.
+
+**Notes**:
+
+1. If you have
+   the [domain restriction org. policy](https://cloud.google.com/resource-manager/docs/organization-policy/restricting-domains)
+   on your organization, you have to edit the `cloud_run_invoker` variable and
+   give it a value that will be accepted in accordance to your policy.
+2. By default, the application will be exposed externally through Global
+   Application Load Balancer, for restricting access to specific identities
+   please check IAP configuration or deploy the application internally via the
+   ILB
+3. Setting the `phpipam_exposure` variable to "INTERNAL" will deploy an Internal
+   Application Load Balancer on the same VPC. This might be the preferred option
+   for enterprises since it prevents exposing the application publicly still
+   allowing internal access through private network (via either VPN and/or
+   Interconnect)
+
+#### Step 3: Deploy resources
+
+Initialize your Terraform environment and deploy the resources:
+
+```shell
+terraform init
+terraform apply
+```
+
+#### Step 4: Use the created resources
+
+Upon completion, you will see the output with the values for the Cloud Run
+service and the user and password to access the application.
+You can also view it later with:
+
+```shell
+terraform output
+# or for the concrete variable:
+terraform output cloud_run_service
+```
+
+Please be aware that the password created in the script is not yet configured in the
+application, you will be prompted to insert that during phpIPAM installation
+process at first login.
+To access the newly deployed application follow these instructions:
+
+1. Get the default phpIPAM url from the terraform output in the form
+   {IP_ADDRESS}.nip.io
+2. Open your browser at that URL and you will see your phpIPAM installation page
+   like the following one:
+
+![phpIPAM Installation page](images/phpipam_install.png "phpIPAM installation page")
+
+3. Click on "New phpipam installation". On the next page click "Automatic
+   database installation", you will be prompted to the following form:
+
+![phpIPAM DB install](images/phpipam_db.png "phpIPAM DB installation")
+
+4. Insert "admin" as the MySQL username and the password available on the
+   terraform output of this command below (without quotes).
+   Untick the "Create new database" otherwise you'll get an error during
+   installation, leave all the other values as default and then click on "
+   Install phpipam database"
+
+```
+terraform output cloudsql_password
+```
+
+5. After some time a "Database installed successfully!" message should pop up.
+   Then click "continue" and you'll be prompted to the last form for configuring
+   admin credentials:
+
+![phpIPAM Admin setup](images/phpipam_admin.png "phpIPAM DB installation")
+
+6. Insert the phpipam password available in the output of the following command
+   and choose a site title. Then insert the site url and click "Save
+   settings". "A Settings updated, installation complete!" message should pop up
+   and clicking "Proceed to login." will redirect you to the login page.
+   Be aware this is just a convenient way to have a backup admin password in
+   terraform, you could use whatever password you prefer.
+
+```
+terraform output phpipam_password
+```
+
+7. Insert "admin" as username and the password configured on the previous step
+   and after login you'll finally get to the phpIPAM homepage.
+
+![phpIPAM Homepage](images/phpipam_home.png "phpIPAM Homepage")
+
+### Cleaning up your environment
+
+The easiest way to remove all the deployed resources is to run the following
+command in Cloud Shell:
+
+``` {shell}
+terraform destroy
+```
+
+The above command will delete the associated resources so there will be no
+billable charges made afterwards.
+<!-- BEGIN TFDOC -->
+## Variables
+
+| name | description | type | required | default |
+|---|---|:---:|:---:|:---:|
+| [prefix](variables.tf#L109) | Prefix used for resource names. | <code>string</code> | ✓ |  |
+| [project_id](variables.tf#L128) | Project id, references existing project if `project_create` is null. | <code>string</code> | ✓ |  |
+| [admin_principals](variables.tf#L19) | Users, groups and/or service accounts that are assigned roles, in IAM format (`group:[email protected]`). | <code>list&#40;string&#41;</code> |  | <code>&#91;&#93;</code> |
+| [cloud_run_invoker](variables.tf#L25) | IAM member authorized to access the end-point (for example, 'user:YOUR_IAM_USER' for only you or 'allUsers' for everyone). | <code>string</code> |  | <code>&#34;allUsers&#34;</code> |
+| [cloudsql_password](variables.tf#L31) | CloudSQL password (will be randomly generated by default). | <code>string</code> |  | <code>null</code> |
+| [connector](variables.tf#L37) | Existing VPC serverless connector to use if not creating a new one. | <code>string</code> |  | <code>null</code> |
+| [create_connector](variables.tf#L43) | Should a VPC serverless connector be created or not. | <code>bool</code> |  | <code>true</code> |
+| [custom_domain](variables.tf#L49) | Cloud Run service custom domain for GLB. | <code>string</code> |  | <code>null</code> |
+| [iap](variables.tf#L55) | Identity-Aware Proxy for Cloud Run in the LB. | <code title="object&#40;&#123;&#10;  enabled            &#61; optional&#40;bool, false&#41;&#10;  app_title          &#61; optional&#40;string, &#34;Cloud Run Explore Application&#34;&#41;&#10;  oauth2_client_name &#61; optional&#40;string, &#34;Test Client&#34;&#41;&#10;  email              &#61; optional&#40;string&#41;&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code>&#123;&#125;</code> |
+| [ip_ranges](variables.tf#L67) | CIDR blocks: VPC serverless connector, Private Service Access(PSA) for CloudSQL, CloudSQL VPC. | <code title="object&#40;&#123;&#10;  connector &#61; string&#10;  psa       &#61; string&#10;  ilb       &#61; string&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code title="&#123;&#10;  connector &#61; &#34;10.8.0.0&#47;28&#34;&#10;  psa       &#61; &#34;10.60.0.0&#47;24&#34;&#10;  ilb       &#61; &#34;10.128.0.0&#47;28&#34;&#10;&#125;">&#123;&#8230;&#125;</code> |
+| [phpipam_config](variables.tf#L81) | PHPIpam configuration. | <code title="object&#40;&#123;&#10;  image &#61; optional&#40;string, &#34;phpipam&#47;phpipam-www:latest&#34;&#41;&#10;  port  &#61; optional&#40;number, 80&#41;&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code title="&#123;&#10;  image &#61; &#34;phpipam&#47;phpipam-www:latest&#34;&#10;  port  &#61; 80&#10;&#125;">&#123;&#8230;&#125;</code> |
+| [phpipam_exposure](variables.tf#L93) | Whether to expose the application publicly via GLB or internally via ILB, default GLB. | <code>string</code> |  | <code>&#34;EXTERNAL&#34;</code> |
+| [phpipam_password](variables.tf#L103) | Password for the phpipam user (will be randomly generated by default). | <code>string</code> |  | <code>null</code> |
+| [project_create](variables.tf#L119) | Provide values if project creation is needed, uses existing project if null. Parent is in 'folders/nnn' or 'organizations/nnn' format. | <code title="object&#40;&#123;&#10;  billing_account_id &#61; string&#10;  parent             &#61; string&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code>null</code> |
+| [region](variables.tf#L133) | Region for the created resources. | <code>string</code> |  | <code>&#34;europe-west4&#34;</code> |
+| [security_policy](variables.tf#L139) | Security policy (Cloud Armor) to enforce in the LB. | <code title="object&#40;&#123;&#10;  enabled      &#61; optional&#40;bool, false&#41;&#10;  ip_blacklist &#61; optional&#40;list&#40;string&#41;, &#91;&#34;&#42;&#34;&#93;&#41;&#10;  path_blocked &#61; optional&#40;string, &#34;&#47;login.html&#34;&#41;&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code>&#123;&#125;</code> |
+| [vpc_config](variables.tf#L149) | VPC Network and subnetwork self links for internal LB setup. | <code title="object&#40;&#123;&#10;  network    &#61; string&#10;  subnetwork &#61; string&#10;&#125;&#41;">object&#40;&#123;&#8230;&#125;&#41;</code> |  | <code>null</code> |
+
+## Outputs
+
+| name | description | sensitive |
+|---|---|:---:|
+| [cloud_run_service](outputs.tf#L17) | CloudRun service URL. | ✓ |
+| [cloudsql_password](outputs.tf#L23) | CloudSQL password. | ✓ |
+| [phpipam_ip_address](outputs.tf#L29) | PHPIPAM IP Address either external or internal according to app exposure. |  |
+| [phpipam_password](outputs.tf#L34) | PHPIPAM user password. | ✓ |
+| [phpipam_url](outputs.tf#L40) | PHPIPAM website url. |  |
+| [phpipam_user](outputs.tf#L45) | PHPIPAM username. |  |
+<!-- END TFDOC -->
+## Test
+
+```hcl
+module "test" {
+  source           = "./fabric/blueprints/third-party-solutions/phpipam"
+  admin_principals = ["group:[email protected]"]
+  prefix           = "test"
+  project_create = {
+    billing_account_id = "1234-ABCD-1234"
+    parent             = "folders/1234563"
+  }
+  project_id = "test-prj"
+}
+# tftest modules=7 resources=43
+```

blueprints/third-party-solutions/phpipam/cloudsql.tf

@@ -0,0 +1,31 @@
+/**
+ * Copyright 2023 Google LLC
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+# Set up CloudSQL
+module "cloudsql" {
+  source           = "../../../modules/cloudsql-instance"
+  project_id       = module.project.project_id
+  name             = "${var.prefix}-mysql"
+  database_version = local.cloudsql_conf.database_version
+  databases        = [local.cloudsql_conf.db]
+  network          = local.network
+  prefix           = var.prefix
+  region           = var.region
+  tier             = local.cloudsql_conf.tier
+  users = {
+    "${local.cloudsql_conf.user}" = var.cloudsql_password
+  }
+}