update gemini-3h release and instance changes

[DaMandal0rian]

PR Type

enhancement

---

Description

• Updated the docker-tag for various configurations in main.tf to "gemini-3h-2024-sep-17".
• Changed instance types for rpc and domain to "m7a.2xlarge" in variables.tf.
• Set instance counts for bootstrap, domain, autoid, nova-squid, evm_bootstrap, and autoid_bootstrap to 0 in variables.tf.

---

Changes walkthrough 📝

Relevant files

Enhancement

main.tf Update Docker tag for Gemini-3h configurations                      resources/gemini-3h/main.tf Updated docker-tag to "gemini-3h-2024-sep-17" for multiple configurations. Added a newline for better readability. +7/-6      variables.tf Modify instance types and counts for Gemini-3h                      resources/gemini-3h/variables.tf Changed instance types for rpc and domain to "m7a.2xlarge". Updated instance counts for several configurations to 0. +8/-7

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Cost optimization	Add conditional checks to prevent deployment of resources when instance count is zero Consider adding a conditional check for instance-count to ensure that configurations with a count of zero do not inadvertently deploy resources. This can prevent unnecessary cloud resource allocation and associated costs. resources/gemini-3h/main.tf [11] -instance-count = var.instance_count["bootstrap"] +instance-count = var.instance_count["bootstrap"] > 0 ? var.instance_count["bootstrap"] : 0 Suggestion importance[1-10]: 9 Why: Adding conditional checks for instance count is a strong suggestion for cost optimization, as it prevents unnecessary resource allocation and potential costs when the instance count is zero.	9
Maintainability	Use a variable for the docker tag to maintain consistency and simplify updates Consider using a variable for the docker-tag to ensure consistency and ease of updates across different configurations. This approach will help maintain the docker tag version in one place and reduce the risk of discrepancies or errors during updates. resources/gemini-3h/main.tf [13] -docker-tag = "gemini-3h-2024-sep-17" +docker-tag = var.docker_tag_version Suggestion importance[1-10]: 8 Why: Using a variable for the docker tag is a good practice for maintainability, as it centralizes the version control and reduces the risk of discrepancies across multiple configurations.	8
Security	Use a variable for the genesis hash to enhance security and flexibility To avoid hardcoding the genesis-hash, consider using a variable or a secure method to inject this value, enhancing the security and flexibility of the configuration. resources/gemini-3h/main.tf [16] -genesis-hash = "0c121c75f4ef450f40619e1fca9d1e8e7fbabc42c895bc4790801e85d5a91c34" +genesis-hash = var.genesis_hash Suggestion importance[1-10]: 8 Why: Using a variable for the genesis hash enhances security by avoiding hardcoding sensitive information, and increases flexibility for future changes.	8
Best practice	Manage the deployment version through a variable for better version control Ensure that the deployment-version is updated or managed through a variable if the deployment process is versioned. This can help in tracking and managing different deployment stages or versions systematically. resources/gemini-3h/main.tf [9] -deployment-version = 0 +deployment-version = var.deployment_version Suggestion importance[1-10]: 7 Why: Managing the deployment version through a variable can improve version control and tracking, especially if the deployment process is versioned, although it may not be as critical if the version is static.	7