@hiiretail/gcp-infra-cli 0.102.0 → 0.102.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,19 +3,41 @@
3
3
  ## Summary
4
4
 
5
5
  <!--
6
- This section should be written last, when all of the other bullets in the RCA has been written. The purpose of this section is to have a section that can be
7
- shared with external customers as well as internal stakeholders. Some guidelines and pointers:
6
+ Briefly summarize what happened, who was impacted (e.g., end-users, stores), and the business consequences (e.g., data loss, incorrect pricing, downtime).
7
+ * Incident Description: Brief overview of what happened (2-3 sentences)
8
+ * Root Cause: One-sentence explanation of the fundamental issue
9
+ * Resolution: Brief description of how the issue was resolved
10
+ * Resolution Time: When the issue was fully resolved
11
+ -->
12
+
13
+ ## Technical Details
14
+
15
+ <!--
16
+ Provide a clear explanation of the technical root cause. Include:
17
+ * What change or event triggered the incident
18
+ * How the system behaved unexpectedly
19
+ * Details about any configuration changes, bugs, or missing logic
20
+
21
+ Any dependencies or services involved.
22
+ -->
8
23
 
9
- * Think of it as the back cover of a book, a short but descriptive story
10
- * The people who will read this will most likeley not have the technical know-how that we do, keep it simple
11
- * Include what the problem was and how the customer(s) was affected
12
- * Do NOT include any customer names
13
- * Do NOT include any Hii Retail service names or underlying technologies that we are using
14
- * Include some general action points, such as if additional alerts needs to be added. Do not add details
15
- * Don't make promises, if there are any actions that we will look at, just mention them. Don't include target dates
24
+ ## Impact
16
25
 
17
- Example:
18
- 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.
26
+ <!--
27
+ Describe the direct and indirect consequences of the incident.
28
+ * Customer Impact: How customers/end-users were affected
29
+ * Business Impact: Financial or operational consequences
30
+ * Duration: Total time the issue persisted
31
+ * Scope: Which systems/users were affected
32
+ -->
33
+
34
+ ## Lessons Learned
35
+
36
+ <!--
37
+ Highlight what could have prevented the incident:
19
38
 
20
- We will look into the process of how we update our configuration in production to mitigate these issues going forward.
39
+ * Gaps in testing
40
+ * Gaps in monitoring
41
+ * Gaps in requirements
42
+ * etc.
21
43
  -->
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hiiretail/gcp-infra-cli",
3
- "version": "0.102.0",
3
+ "version": "0.102.1",
4
4
  "description": "Infrastructure as code generator for GCP.",
5
5
  "main": "src/cli.js",
6
6
  "bin": {