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

Provider Pluggability in Provision Dialogs #7353

Open
agrare opened this issue Sep 29, 2020 · 2 comments
Open

Provider Pluggability in Provision Dialogs #7353

agrare opened this issue Sep 29, 2020 · 2 comments

Comments

@agrare
Copy link
Member

agrare commented Sep 29, 2020

The provision dialogs are filled with calls to specific provider workflow classes such as:
keys = wf.kind_of?(ManageIQ::Providers::Redhat::InfraManager::ProvisionWorkflow) [ref
if wf.kind_of?(ManageIQ::Providers::Vmware::InfraManager::ProvisionWorkflow) [ref]
and
if wf.kind_of?(ManageIQ::Providers::Openstack::CloudManager::ProvisionWorkflow) [ref]

Ideally we should refactor these so that they ask the workflow rather than checking the type of workflow

ManageIQ/manageiq#19440

@skateman
Copy link
Member

skateman commented Sep 29, 2020

The same provisioning dialogs are being rendered for service templates (catalog items) on a per-provider basis, so after I convert those to react, this should be fairly easy.

related issues ManageIQ/manageiq#20603 #6944

@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot added the stale label Feb 27, 2023
@Fryguy Fryguy removed the stale label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants