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
SInce introduction of upload_playbook parameter to PlaybookRunner.run() method, we allow the users to upload the target playbook on their own to a remote resources. However, vars_files and vault_password_file parameters still require local paths and still upload local files to a remote host. We need to change PlaybookRunner.run() interface so that either
all provided paths are local and all the files get uploaded to a remote host automatically or
all provided paths are remote and it's up to the user to get those files to a remote resources
SInce introduction of
upload_playbook
parameter toPlaybookRunner.run()
method, we allow the users to upload the target playbook on their own to a remote resources. However,vars_files
andvault_password_file
parameters still require local paths and still upload local files to a remote host. We need to changePlaybookRunner.run()
interface so that eitherThis should be driven by the value passed to
upload_playbook
parameter. For more context, see my conversation with Lukas here: https://github.com/rhevm-qe-automation/python-rrmngmnt/pull/129/files#r422892028The text was updated successfully, but these errors were encountered: