Add in the manageiq.* automate and vmdb roles

[syncrou]

The roles have been namespaced via the manageiq prefix: manageiq.manageiq-automate and manageiq.manageiq-vmdb.

https://bugzilla.redhat.com/show_bug.cgi?id=1539762

Edit by @NickLaMuro : Updated the description and title to reflect the actual prefix that was commited per this comment: #254 (comment)

[syncrou]

@miq-bot add_label wip, enhancement

@miq-bot assign @Fryguy

cc - @gmcculloug, @gtanzillo

[syncrou]

@miq-bot remove_label wip

[gmcculloug]

@Fryguy I think this is ready to merge. Any remaining issues?

[JPrause]

@Fryguy it appears this can be merged. Can you review.

[jrafanie]

@gmcculloug @syncrou can you drop the WIP from the description of this PR if it's ready?

[syncrou]

@jrafanie - I pulled out the WIP statement.

[jrafanie]

@miq-bot add_label blocker

[Fryguy]

Looks good. Since we are adding a lot of yaml here, it might be good to add the yamllint stuff so that the bot can verify it for us. This way, you don't get churn on your yamls, but I'll leave it up to @gmcculloug on how to proceed, since I know you want this is sooner than later.

[gmcculloug]

@Fryguy Can you point to an example of what is required for yamllint? Depending on the level of effort it could be a follow PR.

[JPrause]

@syncrou can you add the garpindashvili/yes label.

[syncrou]

@miq-bot add_label garpindashvili/yes

[miq-bot]

@syncrou Cannot apply the following label because they are not recognized: garpindashvili/yes

[Fryguy]

@imtayadeway Can you comment on #254 (comment) ?

[Fryguy]

Depending on the level of effort it could be a follow PR.

@gmcculloug Yes, it can be follow up PR. I'm mostly concerned about the churn, which can be distracting in the future, but it's up to you.

[imtayadeway]

@gmcculloug I attempted to answer your question in the form of a PR: #277

[syncrou]

@Fryguy - Everything we discussed for this PR is taken care of.

[Fryguy]

The bot hasn't rerun on this repo, so it hasn't really used the yamllint stuff. The only way to force it is to push a commit (just amend the commit and force push).

[miq-bot]

Checked commit syncrou@d6fd182 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. ⭐

[syncrou]

@Fryguy - Made a couple of changes suggested by the new yamllint rules. Everything is green now again.

[simaishi]

Gaprindashvili backport details:

$ git log -1
commit 3bc2d372216956eea3ff4f3b2584a8f3de4d31b8
Author: Jason Frey <fryguy9@gmail.com>
Date:   Thu Apr 12 11:28:35 2018 -0400

    Merge pull request #254 from syncrou/seed_ansible_playbooks
    
    Add in the miq. automate and vmdb roles
    (cherry picked from commit e045e8c31a30cee9c3f455da7f9221e7f30a504b)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1566658

[NickLaMuro]

Note: Updated the PR title and description to match the changes that were made and mentioned in these comments:

• Add in the manageiq.* automate and vmdb roles #254 (comment)
• Add in the manageiq.* automate and vmdb roles #254 (comment)