feat: add 70% CPU load simulation for realistic demo metrics

[jameslaneovermind]

No description provided.

[env0]

🚀  env0 had composed a PR Plan for environment Terraform Example / production :

Plan: 0 to add, 2 to change, 0 to destroy.

Plan Details

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!   update in-place

Terraform will perform the following actions:


  # module.api_server.aws_instance.api_server[0] will be updated in-place
!   resource "aws_instance" "api_server" {
        id                                   = "i-0ab8548514d9e361b"
!       public_dns                           = "ec2-18-171-170-192.eu-west-2.compute.amazonaws.com" -> (known after apply)
!       public_ip                            = "18.171.170.192" -> (known after apply)
        tags                                 = {
            "CostCenter"  = "engineering"
            "Environment" = "production"
            "ManagedBy"   = "terraform"
            "Name"        = "api-51c748b4-api-server"
            "Project"     = "api-platform"
            "Workload"    = "cpu-intensive"
        }
!       user_data                            = "1ffd9ca91b1b9ea29b17ccb86b019b0e7cfd294b" -> "627f06eeee1e41f87d9e55ae56203ae81058d890"
        # (30 unchanged attributes hidden)

        # (7 unchanged blocks hidden)
    }

  # module.heritage[0].aws_rds_cluster.face_database will be updated in-place
!   resource "aws_rds_cluster" "face_database" {
        id                                    = "facial-recognition-terraform-example"
        tags                                  = {}
        # (46 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 2 to change, 0 to destroy.

Failed to calculate cost estimation

Full PR Plan logs on env0

[github-actions]

Open in Overmind ↗

---

model|risks_v6

🔴 Change Signals

Routine 🔴 ▇▅▃▂▁ First ever modification of attribute user_data

View signals ↗

---

🔥 Risks

[!NOTE] > Overmind has not identified any risks associated with this change
This could be due to the change being low risk with no impact on other parts of the system, or involving resources that Overmind currently does not support.

---

🟣 Expected Changes

~ ec2-instance › i-0ab8548514d9e361b

--- current
+++ proposed
@@ -45,6 +45,6 @@
       hostname_type: ip-name
   private_ip: 10.0.101.88
-  public_dns: ec2-18-171-170-192.eu-west-2.compute.amazonaws.com
-  public_ip: 18.171.170.192
+  public_dns: (known after apply)
+  public_ip: (known after apply)
   root_block_device:
     - delete_on_termination: true
@@ -90,5 +90,5 @@
   terraform_name: module.api_server.aws_instance.api_server[0]
   timeouts: null
-  user_data: 1ffd9ca91b1b9ea29b17ccb86b019b0e7cfd294b
+  user_data: 627f06eeee1e41f87d9e55ae56203ae81058d890
   user_data_base64: null
   user_data_replace_on_change: false

---

---

💥 Blast Radius

Items 115

Edges 265

[github-actions]

⛔ Auto-Blocked

---

🔴 Decision

Auto-blocked: Routine score (-5) is below minimum (-1)

---

📊 Signals Summary

Routine 🔴 -5

---

🔥 Risks Summary

High 0 · Medium 0 · Low 0

---

💥 Blast Radius

Items 115 · Edges 265

---

View full analysis in Overmind ↗