Store registration yaml in installed system

[davidcassany]

This PR ensures the bare minimum configuration to call elemental-operator register from the installed system is stored to the installed system during the installation.

On installed system calling elemental-operator register /oem/registration will rerun the registration process without applying any change on the current system (no installation neither cloud-config download). Can be used to apply labels to machine inventories and similar operations.

Related to rancher/elemental-cli#284 and #63

Signed-off-by: David Cassany [email protected]

[codecov-commenter]

Codecov Report

Merging #71 (8abe9a7) into main (e15e76e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #71   +/-   ##
=======================================
  Coverage   29.74%   29.74%           
=======================================
  Files           5        5           
  Lines         353      353           
=======================================
  Hits          105      105           
  Misses        244      244           
  Partials        4        4           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e15e76e...8abe9a7. Read the comment docs.

[Itxaka]

Looks good, but if its only for the labels, shouldnt we just integrate that as part of the registration? we should have all the info needed to add labels already no? And the machineInventory should already be created? I think we should explore that afterwards but this works for now 👍

[fgiudici]

Looks good, but if its only for the labels, shouldnt we just integrate that as part of the registration? we should have all the info needed to add labels already no? And the machineInventory should already be created? I think we should explore that afterwards but this works for now +1

Yeah, I think the more general question is: the elemental-operator is just for installing the system or should be available after the install (e.g., for labels)?
But sure, if we need to call it after-install, we need to store the Registration URL and ca-cert.

[fgiudici]

LGTM!

[davidcassany]

You both are right indeed, it is not completely clear to me if it makes much sense running elemental-operator register beyond the installation use case, however it is currently handy in our manual tests, at least, to add labels into the machine inventory.