(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=mergify%2Fbp%2Fcircinus%2Fpr-85 2024-10-04T11:02:28+00:00 2024-10-04T11:02:28+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2024-10-04T08:49:36+00:00 urn:sha1:db73f064b794ebb290ad8db7335ae95fedd93ac3 (cherry picked from commit 08200e5f64a17225fca73b9f52b0bc2c27aa938f) 2024-09-14T13:30:16+00:00 Christian Breunig christian@breunig.cc 2024-09-14T13:30:16+00:00 urn:sha1:1fedb993e7f50b30b4232fb1a6c30261dc379543 T6674: Action add trigger workflow to rebuild package 2024-09-14T10:07:06+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2024-09-14T10:07:06+00:00 urn:sha1:2fee3fdf7ec854b87a94fda69fa94afff29ffdb9 2024-07-12T17:33:22+00:00 Daniil Baturin daniil@vyos.io 2024-07-12T17:33:22+00:00 urn:sha1:10aa89ddb0d36dae87ba098ee9b52ebe981ce7f5 SSH KEY: T6568: Fixed adding SSH keys with same comments (backport #78) 2024-07-12T12:49:48+00:00 zsdc taras@vyos.io 2024-07-11T12:04:16+00:00 urn:sha1:d5b2df9ee794feeaf2f606448cb8497f0508f98e 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 <base64> my_user_name ssh-ed25519 <base64> my_user_name ``` (cherry picked from commit c02b1151e584ea6c0bca35ba6aa87504566f6949) 2024-06-07T10:27:59+00:00 zsdc taras@vyos.io 2024-06-06T11:38:44+00:00 urn:sha1:77862f882245a62efef6095e2739d6edfb91d674 Added an unattended installer, compatible with similar from VyOS 1.3. Check the `config/cloud.cfg.d/20_vyos_install.cfg` for configuration details. 2024-05-16T00:13:51+00:00 zsdc taras@vyos.io 2024-05-16T00:12:08+00:00 urn:sha1:70304ff90d931265cb736ace692967242c9b9729 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. 2024-02-22T17:07:16+00:00 zsdc taras@vyos.io 2024-02-22T17:05:59+00:00 urn:sha1:fd8c12784127e3258762d0163455d595b427ea53 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 2024-02-06T14:18:44+00:00 zsdc taras@vyos.io 2024-02-06T14:09:36+00:00 urn:sha1:412287741b70b536458d84972257eda0b3c18d9f 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. 2024-01-01T22:22:33+00:00 Christian Breunig christian@breunig.cc 2024-01-01T22:22:33+00:00 urn:sha1:3e026561f4787d2b6e634b8d170dc3fade85a96f fix to handle OpenStack where mtu exists but is null