Skip to content
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

Generic Service State Machine - new retirement instances. #72

Merged

Conversation

tinaafitz
Copy link
Member

Added new retirement instances for each variation.

Catalog Items with no retirement playbook:
retire_basic_resource <----- UI Default
retire_basic_resource_none

Catalog Items with retirement playbook:
retire_advanced_resource_none <----- UI Default
retire_advanced_resource_pre
retire_advanced_resource_post

https://www.pivotaltracker.com/story/show/141719033

@miq-bot miq-bot added the wip label Mar 14, 2017
@tinaafitz tinaafitz force-pushed the generic_service_retirement_instances branch from dfa8acf to c447ae9 Compare March 22, 2017 13:26
@tinaafitz tinaafitz changed the title [WIP]Generic Service State Machine - new retirement instances. Generic Service State Machine - new retirement instances. Mar 22, 2017
@miq-bot miq-bot removed the wip label Mar 22, 2017
@miq-bot
Copy link
Member

miq-bot commented Mar 22, 2017

Checked commit tinaafitz@c447ae9 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
0 files checked, 0 offenses detected
Everything looks good. 👍

@tinaafitz
Copy link
Member Author

@mkanoor Please review.

@gmcculloug
Copy link
Member

Travis failures are related to issue ManageIQ/manageiq#14393 which is being addressed in PR ManageIQ/manageiq#14478.

@gmcculloug gmcculloug merged commit 16cc1c3 into ManageIQ:master Mar 24, 2017
@gmcculloug gmcculloug added this to the Sprint 57 Ending Mar 27, 2017 milestone Mar 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants