fix variable information

[kevinbleckmann]

User description

fix the variables for C4 and N4 as not required to manage min cpu

---

PR Type

enhancement, bug fix

---

Description

• Added machine_type configuration for Intel Confidential Compute VM with TDX in examples/gcp-linux-tdx-vm/main.tf.
• Removed unsupported n4 and c4 machine types from main.tf.
• Added a newline at the end of examples/gcp-linux-vm/variables.tf for formatting consistency.

---

Changes walkthrough 📝

	Relevant files
Enhancement	main.tf Add machine type configuration for TDX VM                                examples/gcp-linux-tdx-vm/main.tf Added machine_type variable with value c3-standard-4. Ensured proper configuration for Intel Confidential Compute VM with TDX. +2/-0
Formatting	variables.tf Add newline at end of variables file                                          examples/gcp-linux-vm/variables.tf Added a newline at the end of the file. +2/-1
Bug fix	main.tf Remove unsupported machine types from configuration            main.tf Removed n4 and c4 machine types from the list. Updated machine type mapping to exclude unnecessary entries. +2/-3

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Configuration Update The addition of machine_type as "c3-standard-4" should be validated to ensure it aligns with the project's requirements for Intel Confidential Compute VM with TDX. Syntax Error The closing bracket for the variable "project" was added, but it seems to be redundant as the variable block was already properly closed. Removal of Machine Types The removal of "n4" and "c4" machine types needs to be confirmed if it aligns with the project's future direction and compatibility with existing deployments.

[daveshrestha-intel]

Done

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Add meaningful values or descriptions for new machine types Provide a valid value or description for the new machine types "n4" and "c4" instead of setting them to null, to ensure they are properly utilized and described within the infrastructure. main.tf [22-23] -"n4": null -"c4": null +"n4": "Description or valid value" +"c4": "Description or valid value" Suggestion importance[1-10]: 8 Why: Providing valid values or descriptions for the new machine types "n4" and "c4" is important for clarity and proper utilization within the infrastructure. This suggestion enhances the code by ensuring all machine types are well-defined.	8
Possible issue	Validate the machine_type format to match the defined regex Ensure that the machine_type value "c3-standard-4" matches the expected format defined by machine_type_regex in the main.tf of the root module to maintain consistency and prevent runtime errors. examples/gcp-linux-tdx-vm/main.tf [20] -machine_type = "c3-standard-4" +machine_type = "c3-standard-4" # Ensure this matches the regex "^([cemn][1234u])" Suggestion importance[1-10]: 7 Why: The suggestion highlights the importance of ensuring that the machine_type value matches the expected regex format, which is crucial for consistency and preventing runtime errors. However, the suggestion is not actionable as it only adds a comment without verifying the format.	7