Closed donnydavis closed 4 years ago
@ahkok Is this approach viable? Let me know if I can help.
@ahkok Do you think it would be best to have a rule that takes care of import and then seperate rules that handle the different cloud providers with proper options for each?
@ahkok Any updates?
I've spent some significant time on this in the last 2-3 days. No resolution yet, unfortunately.
Did we ever validate this properly? It looks like we need this in the end anyway for -native kernels and I might just include it in the bundle by default (the risk of double-parsing the config-2 file system is minimal).
We just need to know it actually functions.
--user-data-once
doesn't help if the SSH keys are in meta_data.json
. We should figure out a way to solve that, too.
@ahkok If you need any help testing please lmk.
This is now obsolete - we modprobe sr_mod to force any locally attached config-2 filesystem to appear explicitly in case it isn't found.
This PR is to create a udev rule that imports the FS_LABEL so udev can recognize config-2.
Resolves: https://github.com/clearlinux/micro-config-drive/issues/40