@hiiretail/gcp-infra-cli 0.93.0 → 0.94.0

package/generators/common-resources/budget/generator.json

@@ -0,0 +1,4 @@
+{
+  "name": "GCP Budget",
+  "description": "Create a budget and alert notifications"
+}

package/generators/common-resources/budget/index.js

@@ -0,0 +1,42 @@
+const path = require('path');
+const chalk = require('chalk');
+const BaseGenerator = require('../../../src/BaseGenerator');
+
+module.exports = class extends BaseGenerator {
+  prompting() {
+    const prompts = [
+      {
+        type: 'input',
+        name: 'monitoringNotificationChannels',
+        message: 'Enter a comma-separated list of monitoring notification channels (format: projects/{project_id}/notificationChannels/{channel_id}). At least one email address must be included. Up to 5 channels are permitted.',
+      },
+    ];
+    return this.prompt(prompts).then((props) => {
+      this.answers = props;
+    });
+  }
+
+  writing() {
+    const channelsArray = this.answers.monitoringNotificationChannels ? this.answers.monitoringNotificationChannels.split(',').map((channel) => channel.trim()) : [];
+
+    ['prod', 'staging'].forEach((env) => {
+      this.copyDir(
+        'budget',
+        path.join('infra', env, 'budget'),
+        {
+          ...this.answers,
+          env,
+          monitoringNotificationChannels: channelsArray,
+        },
+      );
+    });
+  }
+
+  end() {
+    this.log(`
+${chalk.green('Your budget has been created.')}
+${chalk.green('1.')} To finalize your configuration, please continue with manual editing of the generated files.
+${chalk.green('2.')} Push the changes in a feature branch and open a pull request.
+`);
+  }
+};

package/generators/common-resources/budget/templates/budget/terragrunt.hcl

@@ -0,0 +1,28 @@
+# Terragrunt will copy the Terraform configurations specified by the source parameter, along with any files in the
+# working directory, into a temporary folder, and execute your Terraform commands in that folder.
+terraform {
+  source = "git::https://github.com/extenda/terraform-google-project-factory//modules/budget?ref=feat/CNP-25"
+}
+
+# Include all settings from the root terragrunt.hcl file
+include {
+  path = find_in_parent_folders("terragrunt_root.hcl")
+}
+
+locals {
+  project_vars = read_terragrunt_config(find_in_parent_folders("project.hcl"))
+  common_vars  = read_terragrunt_config(find_in_parent_folders("common.hcl"))
+}
+
+# These are the variables we have to pass in to use the module specified in the terragrunt configuration above
+inputs = merge(
+  {
+    projects                         = [local.project_vars.locals.project_id]
+    display_name                     = "${local.project_vars.locals.project_name}-budget"
+    billing_account                  = "01580F-3DD16A-C066A5"
+    amount                           = local.project_vars.locals.amount
+    monitoring_notification_channels = <%-JSON.stringify(monitoringNotificationChannels)%>
+    disable_default_iam_recipients   = true
+    alert_spent_percents             = [0.8, 1.0, 1.2]
+  }
+)

package/generators/docs/rca/templates/docs/rca_external.md

@@ -11,9 +11,11 @@ shared with external customers as well as internal stakeholders. Some guidelines
 * Include what the problem was and how the customer(s) was affected
 * Do NOT include any customer names
 * Do NOT include any Hii Retail service names or underlying technologies that we are using
-* Include some general action points, such as if additional alerts needs to be added. Skip the details
+* Include some general action points, such as if additional alerts needs to be added. Do not add details
 * Don't make promises, if there are any actions that we will look at, just mention them. Don't include target dates
 
 Example:
 On January 25 2023 from 14:31 CET to 15:59 CET some customers may have experienced delays with card payments. The issue was traced back to a misconfiguration of a recent deployment. At 15:31 CET a fix was deployed and monitored. At 15:59 CET the issue was resolved for all affected customers.
+
+We will look into the process of how we update our configuration in production to mitigate these issues going forward.
 -->

package/generators/docs/rca/templates/docs/rca_internal.md

@@ -12,9 +12,15 @@
 
 **Impact to customer**: <!-- Describe how the customer, and end customers, was affected by the incident. Where they completely unable to use the system? Or was there some feature that wasn't working? -->
 
-**Ticket information**: <!-- Add link(s) to any Jira issues -->
+**Ticket information**:
 
-**Services involved**: <!-- List the Hii Retail-service(s) that were involved in the incident, for example checkout-poslog -->
+<!-- Add link(s) to any Jira issues in the format of:
+
+  - [EXTINTERAL-1234](https://extendaretail.atlassian.net/browse/EXTINTERAL-1234)
+
+-->
+
+**Services involved**: <!-- List the Hii Retail-service(s) that were involved in the incident, for example checkout-poslog. If multiple services/systems are involved, just mention the systems such as: Checkout Engine, Store Data etc. -->
 
 ## Summary
 
@@ -31,10 +37,10 @@ Describe the events that caused the incident, starting from when the issues star
 
 Example:
 
-  - 2022-06-14 14.36 - Alert X was triggered
-  - 2022-06-14 14.36 - Team started working on the incident
-  - 2022-06-14 14.49 - A fix was pushed and deployed
-  - 2022-06-14 14.53 - Incident was resolved
+  - 2024-03-27 14.36 CET - Alert X was triggered
+  - 2024-03-27 14.36 CET - Team started working on the incident
+  - 2024-03-27 14.49 CET - A fix was pushed and deployed
+  - 2024-03-27 14.53 CET - Incident was resolved
 -->
 
 ## Five Whys
@@ -42,9 +48,11 @@ Example:
 <!--
 Five whys is a technique used to explore the cause and effect underlying a particular problem. The primary goal of the technique is to determine the root cause of a problem by repeating the question "Why?". Each answer forms the basis of the next question.
 
+Note: It is not a requirement to add exactly 5 whys. If the root cause is found at the third why, it is not necessary to continue. The main point is to find the root cause within 5 steps.
+
 Example:
 
-Problem: The vehicle won't start
+**Problem**: The vehicle won't start
 
   1. __Why?__ - The battery is dead (First why)
   2. __Why?__ - The alternator is not functioning (Second why)
@@ -53,6 +61,8 @@ Problem: The vehicle won't start
   5. __Why?__ - The vehicle was not maintained according to the recommended service schedule. (Fifth why, the root cause)
 -->
 
+**Problem**:
+
   1. __Why?__
   2. __Why?__
   3. __Why?__

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hiiretail/gcp-infra-cli",
-  "version": "0.93.0",
+  "version": "0.94.0",
   "description": "Infrastructure as code generator for GCP.",
   "main": "src/cli.js",
   "bin": {