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

[WIP] Add a data migration for orch stacks to have direct ownership concept #293

Conversation

d-m-u
Copy link
Contributor

@d-m-u d-m-u commented Oct 16, 2018

@tinaafitz this is silly.

Orch stacks should have owners and tenants and groups just like services n vms so when we retire them the stack has some concept of who owns the request.

WIP cause questions in PR and needs tests n stuff

Related to #288 and ManageIQ/manageiq#17951

@miq-bot miq-bot added the wip label Oct 16, 2018
@d-m-u d-m-u force-pushed the a_data_ata_migration_for_orch_stack_ownership branch from 347b2fa to 0ee6cac Compare October 16, 2018 14:00
@miq-bot
Copy link
Member

miq-bot commented Oct 16, 2018

Checked commit d-m-u@0ee6cac with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

Copy link
Member

@bdunne bdunne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like it belongs in #288

@d-m-u d-m-u closed this Oct 16, 2018
@d-m-u d-m-u deleted the a_data_ata_migration_for_orch_stack_ownership branch October 16, 2018 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants