-
Notifications
You must be signed in to change notification settings - Fork 28
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
Don't start evmserverd if messaging is not configured #196
Don't start evmserverd if messaging is not configured #196
Conversation
51c2070
to
0fab933
Compare
say e.result.output | ||
say e.result.error | ||
say "" |
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.
where is say
defined? or is it a global method?
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 see this used everywhere, can check where it is defined though
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 assume it comes from highline globally.
Love the refactoring, but wondering if that should be a separate PR? I'm having trouble separating the refactor from the "Dont start evmserverd if messaging not configured" |
Oh nvm, I didn't see that the "depends on" actually was "built on" (I assumed it was an independent PR). |
00d4abb
to
19c4f04
Compare
#195 is merged |
19c4f04
to
c3dff5a
Compare
def configure_messaging_type(value) | ||
say(__method__.to_s.tr("_", " ").titleize) | ||
|
||
ManageIQ::ApplianceConsole::Utilities.rake_run!("evm:settings:set", ["/prototype/messaging_type=#{value}"]) | ||
end | ||
|
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.
NOTE this will be the default (once ManageIQ/manageiq#21997 is merged) and will not need to be set by appliance console
9b6a8d4
to
1327aca
Compare
Checked commits agrare/manageiq-appliance_console@c3dff5a~...1327aca with ruby 2.6.10, rubocop 1.28.2, haml-lint 0.35.0, and yamllint |
Okay ran a live test setting up an appliance and works as expected, taking out of WIP |
Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195) - Don't start evmserverd until messaging is configured (ManageIQ#196)
Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195) - **BREAKING** Don't start evmserverd until messaging is configured (ManageIQ#196)
Breaking - Don't start evmserverd until messaging is configured (ManageIQ#196) Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195)
Breaking - Don't start evmserverd until messaging is configured (ManageIQ#196) Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195)
Breaking - Don't start evmserverd until messaging is configured (ManageIQ#196) Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195)
Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195) - Don't start evmserverd until messaging is configured **BREAKING** (ManageIQ#196) - Simplify messaging options by saving in yml files (ManageIQ#197)
Fixed - Don't require pressing any key twice for message configuration (ManageIQ#193) Added - Report messaging configuration on summary info page (ManageIQ#190) Changed - Refactor EvmServer operations (ManageIQ#194) - Only start evmserverd after all application configuration is done (ManageIQ#195) - **BREAKING** Don't start evmserverd until messaging is configured **BREAKING** (ManageIQ#196) - Simplify messaging options by saving in yml files (ManageIQ#197)
Only start evmserverd once database and messaging have been configured
NOTE added a third state to
ManageIQ Server
:running, not running, not configured
so it is consistent with the database statusDepends on:
Required for: