f445e3c606
The example was showing how to use the `files` option to pass in a local file as an authorized public key for root. While this works, it's a bit sloppy, given that there's a specific option, `key_name` which will use one of your public keys on your rackspace account and add it as an authorized key for root. In our case, one of our admins didn't notice the `key_name` option because they scrolled straight to the example and saw the `files` strategy. I propose that the example still shows `files`, but not using a root public key as an example, and instead also demonstrate the `key_name` option so that it's clear from the example how to get the initial root public key deployed. |
||
---|---|---|
.. | ||
cloud | ||
commands | ||
database | ||
files | ||
internal | ||
inventory | ||
messaging | ||
monitoring | ||
net_infrastructure | ||
network | ||
notification | ||
packaging | ||
source_control | ||
system | ||
utilities | ||
web_infrastructure | ||
windows |