vyos-cloud-init.git/cloudinit/config, branch current

SSH KEY: T6568: Fixed adding SSH keys with same comments

2024-07-12T12:49:07+00:00

If a key with the same comment already exists in a configuration, generate a new ID for a new one. Example of such a case: ``` ssh-rsa my_user_name ssh-ed25519 my_user_name ```

vyos_install: T5220: Added unattended installer

2024-06-07T10:27:59+00:00

Added an unattended installer, compatible with similar from VyOS 1.3. Check the `config/cloud.cfg.d/20_vyos_install.cfg` for configuration details.

ifupdown: T6038: Cleanup network config properly

2024-05-16T00:13:51+00:00

Cloud-init in environments where Meta-data is available via network configures the main interface and keeps the config in `/etc/network/interfaces.d/`. This config later interferes with the VyOS configuration. To avoid the problem previously the code in the `cc_vyos.py` module was used, but this is not enough. The module is running only once during instance deployment. But Cloud-init will re-add the config file with each boot. There are two ways to solve this incompatibility (within Cloud-init) - disable network config or perform cleanup during each boot. Disabling network config is not correct in this context, because it blocks the ability to fetch Meta-data after the first boot, which in turn blocks the ability to run per-boot modules with an updated config. Therefore, the cleanup code was extracted to an independent `cc_vyos_ifupdown.py` module that performs proper cleanup with each boot.

cc_vyos: T6039: Fixed CLI config for 1.4+

2024-02-22T17:07:16+00:00

Improperly generated configuration can break the configuration process. This fix updates CLI items from the old to the current syntax. Fixed CLI config items for: - NTP servers - HTTPS API - domain-search

cc_vyos: T6007: Run config migrations before Cloud-init

2024-02-06T14:18:44+00:00

Configuration in `vyos_config_commands` is expected to use a syntax from the target VyOS version. But, if Cloud-init applies configuration commands to a default file, all the migrations (from the 0 version to the latest) will still be executed on top of it. This process can break proper config, for example, if the current syntax variant partially repeats one of the older ones, which will trigger a migration without need.

fix to handle OpenStack where mtu exists but is null

2024-01-01T17:39:15+00:00

cc_vyos: T5862: Fixed network configuration

2023-12-28T12:38:00+00:00

- added extra check for maximum supported MTU to avoid exceeding it during configuration - remove udev rules created by cloud-init after initialization - fixed logic for config file selection

SSH: T5235: Made SSH comment parser stricter

2023-05-22T15:05:07+00:00

To avoid problems with SSH public key comments with special characters the parser now generates UUID names for keys if a comment contains anything except `[a-zA-Z0-9_]`.

network: T5012: Added a new option for network-config control

2023-02-16T16:13:19+00:00

A new option for Cloud-Init was added: ``` vyos_config_options: network_config: ``` Possible values: * by default - equal to the `network['config']` from the active Cloud-Init configuration * `enabled` - configure networking, even if global `network['config']` is set to `disabled` * `disabled` - do not configure networking, regardless of global `network['config']` value

Merge pull request #59 from zdc/T4954-sagitta

2023-01-27T15:08:20+00:00

network-config: T4954: Fixed DNS settings