Public bug reported:
per default the salt minion does create the minion_id file with the
short hostname if it does not exist on its first startup. in some
environments the salt minion id is required to be a fully qualified
domain name. therefore i recommend to have a salt minion cloud-config
parameter that allows to be set to true/false and based on the value
takes the FQDN or the shortname and writes it to the minion_id file.
alternatively the minion id could also be fully configurable. meaning:
the whole config string is taken and written to the minion_id file.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1755204
Title:
make salt minion id more configurable
Status in cloud-init:
New
Bug description:
per default the salt minion does create the minion_id file with the
short hostname if it does not exist on its first startup. in some
environments the salt minion id is required to be a fully qualified
domain name. therefore i recommend to have a salt minion cloud-config
parameter that allows to be set to true/false and based on the value
takes the FQDN or the shortname and writes it to the minion_id file.
alternatively the minion id could also be fully configurable. meaning:
the whole config string is taken and written to the minion_id file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1755204/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
