You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some situations where it is possible to have a cluster with different BMC login information. In these situations, it would be necessary to be able to specify each individual node's login information opposed to only using to the one specified currently.
Possible Solutions
There are at least three approaches to consider here. We can specify the BMC login information via:
the YAML config file
environment variables
CLI flags
In the config file, the format may look something like this:
The new method would obsolete the old --username and --password flags in favor of a single --login flag instead.
Other Considerations
Specifying the login information in the config file may not be ideal unless the config file exists in a location that requires elevated admin privileges. Therefore, it may be more advantageous to use environment variables or CLI flags as mentioned above in the "Possible Solutions" section.
davidallendj
changed the title
Add ability to specify each node's user name, password, and hosts if known
[FEATURE] Add ability to specify each node's user name, password, and hosts if known
Jul 18, 2024
Description of Issue
There are some situations where it is possible to have a cluster with different BMC login information. In these situations, it would be necessary to be able to specify each individual node's login information opposed to only using to the one specified currently.
Possible Solutions
There are at least three approaches to consider here. We can specify the BMC login information via:
In the config file, the format may look something like this:
The corresponding environment variable may look similar as a single comma-delimited string with syntax "host:username:password":
And finally, the CLI flags:
The new method would obsolete the old
--username
and--password
flags in favor of a single--login
flag instead.Other Considerations
Specifying the login information in the config file may not be ideal unless the config file exists in a location that requires elevated admin privileges. Therefore, it may be more advantageous to use environment variables or CLI flags as mentioned above in the "Possible Solutions" section.
Migrated from https://github.com/bikeshack/magellan/issues/6.
The text was updated successfully, but these errors were encountered: