I would like to propose an enhancement aimed at expanding the existing capabilities of cloud-init integration within Cockpit-machines. While the current interface supports basic cloud-init settings such as setting usernames and passwords, it lacks the ability to submit a complete cloud-init YAML configuration directly.
To address this, I have developed a feature that allows users to directly input or paste their entire cloud-init YAML configuration (see attached screenshot). This new field offers greater flexibility and enables users to utilize the full capabilities of cloud-init without restrictions.
Ideally, it would be preferable if all cloud-init functionalities could be configured directly via the form interface in Cockpit-machines. However, considering the vast number of configurable options available in cloud-init, it is not practical to provide a dedicated form field for each setting.
If this direction is accepted, I will refine the code, form and create pull request.
I would appreciate your feedback on this proposal.
Hello cockpit-machines maintainers and community,
I would like to propose an enhancement aimed at expanding the existing capabilities of cloud-init integration within Cockpit-machines. While the current interface supports basic cloud-init settings such as setting usernames and passwords, it lacks the ability to submit a complete cloud-init YAML configuration directly.
https://github.com/nxzz/cockpit-machines/commit/87c0ba05dfa2344e415c9f48d4a63cb6cf328b9e
To address this, I have developed a feature that allows users to directly input or paste their entire cloud-init YAML configuration (see attached screenshot). This new field offers greater flexibility and enables users to utilize the full capabilities of cloud-init without restrictions.
Ideally, it would be preferable if all cloud-init functionalities could be configured directly via the form interface in Cockpit-machines. However, considering the vast number of configurable options available in cloud-init, it is not practical to provide a dedicated form field for each setting.
If this direction is accepted, I will refine the code, form and create pull request.
I would appreciate your feedback on this proposal.
Thank you.