fix: add hostname to user-data

[NichArchA82]

PR Type

Bug fix, Enhancement

---

Description

• Added hostname configuration to user-data for VMs.

• Enabled management of /etc/hosts in user-data.

• Enhanced cloud-init script with hostname and hosts management.

---

Changes walkthrough 📝

	Relevant files
Enhancement	get-user-data.js Add hostname and manage `/etc/hosts` in user-data                command-handler/src/util/get-user-data.js Added hostname configuration to the user-data template. Enabled manage_etc_hosts in the cloud-init configuration. Updated runcmd to use the hostname dynamically. +2/-0

---

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

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Input Validation The serverName parameter is used directly in the template string without any validation or sanitization. Invalid hostnames could cause cloud-init failures. hostname: ${serverName} manage_etc_hosts: true

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Implement input validation for hostname to prevent security vulnerabilities and ensure compliance with hostname format standards Sanitize the serverName parameter before using it in the hostname configuration to prevent command injection and ensure valid hostname format. command-handler/src/util/get-user-data.js [9] -hostname: ${serverName} +hostname: ${serverName.replace(/[^a-zA-Z0-9-]/g, '-').toLowerCase().substring(0, 63)} Apply this suggestion Suggestion importance[1-10]: 9 Why: This is a critical security enhancement that prevents command injection and ensures valid hostname format compliance, which is essential for cloud-init configuration reliability and system security.	9
Possible issue	Add parameter validation to prevent undefined values from causing runtime errors Add error handling for undefined or null serverName parameter to prevent runtime errors in the cloud-init configuration. command-handler/src/util/get-user-data.js [6] export default function configUserData(serverName) { + if (!serverName) throw new Error('Server name is required for user data configuration'); Apply this suggestion Suggestion importance[1-10]: 8 Why: Adding validation for the required serverName parameter is crucial to prevent runtime errors in cloud-init configuration, which could lead to system initialization failures.	8