-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
add optional Cloud-init support to Debian VM script #5137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
And why? What advantages do you see for the average user? Cloud Init requires additional settings and the Debian script (as it is currently), is immediately ready for use and immediately available for the average user at any time directly and without detours |
IMO it is way easier to set up a VM with Cloud-init. You can set the login information, network settings and even ssh keys way easier than logging in the VM and setting everything up by hand. It is also not best practice to roll out a VM without a password. |
Maybe we should add an read -p before? So the User can choose. Maybe for Ubuntu too? For example, I personally prefer to use the nocloud images rather than the cloud init scripts. It's simply much easier, especially for quick developments or tests |
Yeah, letting the user choose would probably be a good idea |
Can you prepare the PR for this? Maybe you can test it in VED (other Repo), or directly here |
Sure thing! I will turn this PR into a draft until I'm done |
Changed the script to ask for Cloud-init in the advanced settings. Defaults to no |
✍️ Description
Edit to the Debian VM script to be able to use the "Generic Cloud" image instead of no cloud to use Cloud-init. The script asks for Cloud-init in the advanced settings. It defaults to no.
🔗 Related PR / Issue
Link: # N/A
✅ Prerequisites (X in brackets)
🛠️ Type of Change (X in brackets)
README
,AppName.md
,CONTRIBUTING.md
, or other docs.