Comment 1 for bug 1637308

Actually I think it will work fine because the role list logic looks at the ResourceGroup names (which are still generated for custom roles), but we should still look at reworking this as it's a fragile and indirect relationship which we currently use (instead we should simply parse the list of names from the roles_data.yaml in the plan.