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
fixes #8867 - fixes activation key dynflow update passing in nil variables #4904
Conversation
56e717d
to
3f63e5f
Compare
@@ -15,15 +15,27 @@ module Katello | |||
module ActivationKey | |||
class Update < Actions::EntryAction | |||
def plan(activation_key, activation_key_params) | |||
cp_call = cp_changed?(activation_key.auto_attach, activation_key_params[:auto_attach]) || | |||
cp_changed?(activation_key.service_level, activation_key_params[:service_level]) || | |||
cp_changed?(activation_key.release_version, activation_key_params[:release_version]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might wrap this in a function call itself as well, so that further down you could just do:
if update_candlepin?(activation_key, params)
....
...
end
This encapsulates the logic and allows anyone reading the code to skip over this chunk if they don't need to see the details of it.
A test for the dynflow action would be nice to provide basic confirmation that the Candlepin update task is called in the right scenario and not called in the other scenario. |
3f63e5f
to
917cff8
Compare
@ehelms - I added tests for the update actions in Katello, wrote tests for all three Dynflow case actions in Candlepin, encapsulated (and commented) code inside the Dynflow update function. Let me know if you have any other questions/suggestions! |
917cff8
to
f8a3551
Compare
Tested and worked great for me! ACK |
fixes #8867 - fixes activation key dynflow update passing in nil variables
No description provided.