-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Build: handle awesome spawn update #22772
Conversation
We probably want to move to stub_good/bad_run here - cc @agrare |
@kbrock Can you also change the gem reference to enforce 1.6.0 as a minimum version? This will fail in the reverse direction is the old gem is still used. |
Checked commit kbrock@2a509aa with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint |
Darn. We do not depend upon awesome spawn. Would prefer not to add it. Agree with the need though. researching |
If we use it in core code I think we have to have it in our Gemfile |
It's probably in manageiq-gems-pending. |
Did try this but it got in my way: #require "awesome_spawn/spec_helper"
# include AwesomeSpawn::SpecHelper
# anything = Pathname.new(...)
it "runs ansible-runner with the role" do
expect(Ansible::Runner).to receive(:async?).and_return(false)
stub_good_run!("ansible-runner", :env => a_hash_including(env_vars),
:params => ["start", anything(), :json, {:ident => "result", :role => role_name, :roles_path => role_path, :role_skip_facts => nil}]
)
described_class.run_role_async(env_vars, extra_vars, role_name, :roles_path => role_path)
end |
Backported to
|
Fix Build: handle awesome spawn update (cherry picked from commit 8fb050f)
handle change in attributes passed to
CommandResult#initialize