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
As an example, in kitchen-ec2, there is a facility for automatically fetching the Administrator password for use over winrm, which kitchen then uses to connect to the instance following provisioning, install the client, and continue the run:
Can something analogous be implemented in kitchen-openstack ? If not, or in either case, what is the recommended way of testing on Windows using kitchen-openstack ? As related to authentication, in particular when the Windows Administrator password is randomly generated upon creation.
Currently, the thought is to use cloud_config to add a new user and specify those credentials under transport, but this method has some drawbacks, as does doing the same with user_data. Is there a better approach?
The text was updated successfully, but these errors were encountered:
As an example, in
kitchen-ec2
, there is a facility for automatically fetching the Administrator password for use overwinrm
, whichkitchen
then uses to connect to the instance following provisioning, install the client, and continue the run:https://github.com/test-kitchen/kitchen-ec2#winrm :
Part of the implementation resides here:
https://github.com/test-kitchen/kitchen-ec2/blob/v3.10.0/lib/kitchen/driver/ec2.rb#L567-L580
Can something analogous be implemented in
kitchen-openstack
? If not, or in either case, what is the recommended way of testing on Windows usingkitchen-openstack
? As related to authentication, in particular when the Windows Administrator password is randomly generated upon creation.Currently, the thought is to use
cloud_config
to add a new user and specify those credentials undertransport
, but this method has some drawbacks, as does doing the same withuser_data
. Is there a better approach?The text was updated successfully, but these errors were encountered: