delete ssh-private-key from yaml after processing about azure-li-services HOT 4 CLOSED

alternative the key reading can be changed such that the key is not stored in the yaml file but as a file on the external location where the yaml file itself resides. The yaml file would then only contain a reference to that location.

from azure-li-services.

So this is basically a question for @jeffaco

1. do we want to handle the key as extra file on lun (or iso)
2. do we want to handle the key as element in the config file

I would prefer 1.

from azure-li-services.

If I'm already creating a LUN with the YAML (or a DVD with the YAML), then it seems easy enough do provide the key as an extra file.

It shouldn't be any harder for me, and it eliminates the cleanup issue for you (copy the YAML, don't otherwise worry about it).

So my vote would be for 1 as well.

from azure-li-services.

👍 great I'll change the code to reflect this. Thanks

from azure-li-services.