Combine Embedded Automation Managers

[agrare]

Currently ManageIQ has two embedded automation managers: Embedded Ansible and Embedded Workflows. These are both EmbeddedAutomationManager types but the UI was originally designed with embedded_ansible as a separate / standalone menu-item.

We are looking at adding an additional embedded provider, Embedded Terraform.

As we add more of these it becomes more and more unwieldy to manage each of them separately. It is highly likely that an organization will have repositories / credentials that are common across the three and currently these have to be added to each embedded provider separately.

There are two high-level efforts, core and UI

UI

• Refactor the current controllers and menu-items to not be "Embedded Ansible" or "Embedded Workflows" specific, but rather generic Automation Managers
• Allow management of Git Repositories separate from ConfigurationScriptSource (allow one git repo to have playbooks, ASLs, terraform scripts, etc...)

Core

• Group current embedded automation managers under a "parent" ManageIQ::Providers::EmbeddedAutomationManager
• Allow credentials to be shared across child managers
• Allow for multiple configuration-script-sources per git repo (might already be possible)
• Allow for directory backed configuration-script-sources for built-in automation scripts

[agrare]

cc @Fryguy

[Fryguy]

I think we need to also figure out how to deal with things that are unique to one child type vs another. For example

• Workflows has credential mapping to env vars, but the others do not (or maybe they could!)
• Workflows presents the output of the ASL with a graph, but we'd want to not do that for the other types. When we discussed this I think we said this is better handled automatically by whatever presents code to only do this for ASL files. As such, this is a UI task when consolidating if it isn't done already.

[miq-bot]

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.

[miq-bot]

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.

[miq-bot]

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.

[miq-bot]

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.