I am in the process of adding cloud-init support to Armbian.
Cloud Init is industry standard for customizing virtual targets, but with the NoCloud source it is also possible to use it to customize physical devices. Ubuntu's official Raspberry Pi distributions use it for some time.
I believe the best way to adopt it for Armbian would be to move Armbian_First_Run scripts to an optional extension and then create an extension that provides Cloud Init. It does not make sense to have 2 different, and possibly competing, initialization systems on the same target.
Cloud Init requires the existence of a FAT partition, which is identified by label. PIs use the boot partition, but it is also posisible to use a partition for the purpose, will be identified by label.
I am in the process of adding cloud-init support to Armbian.
Cloud Init is industry standard for customizing virtual targets, but with the NoCloud source it is also possible to use it to customize physical devices. Ubuntu's official Raspberry Pi distributions use it for some time.
I believe the best way to adopt it for Armbian would be to move Armbian_First_Run scripts to an optional extension and then create an extension that provides Cloud Init. It does not make sense to have 2 different, and possibly competing, initialization systems on the same target.
Cloud Init requires the existence of a FAT partition, which is identified by label. PIs use the boot partition, but it is also posisible to use a partition for the purpose, will be identified by label.