Skip to content
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.

Option to use config file for user, password, bearer-token #2

Open
Kybeer opened this issue Feb 11, 2022 · 0 comments
Open

Option to use config file for user, password, bearer-token #2

Kybeer opened this issue Feb 11, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@Kybeer
Copy link

Kybeer commented Feb 11, 2022

Is your feature request related to a problem? Please describe.

I would like to avoid putting the user, password, bearer-token in the container environmental variables when starting it

Is there an option to specify a configuration file with those parameters instead?

Describe the solution you'd like

Option to specify environmental variables like this into a configuration file:

Variables Default Value Notes
VCENTER (not set) The vCenter IP address
VCPORT 443 The vCenter Port
VCUSER (not set) The username for vCenter login
VCPASSWORD (not set) The password for vCenter login
CLUSTERNAME (not set) The cluster name in vCenter
BEARER_TOKEN (not set) The bearer token used for authorization, will be generated automatically if not set

and

Short option Long option Description
-s --host Remote host to connect to (vCenter address)
-0 --port Port to connect on (vCenter address) with default 443
-u --username vSphere (vCenter) user name
-p --password vSphere (vCenter) password
-c --cluster The vSAN cluster name with default VSAN-Cluster

Describe alternatives you've considered

No response

Additional context

No response

@Kybeer Kybeer added the enhancement New feature or request label Feb 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant