Role handling

[lechnerc77]

Fixing bugs from role handling - see issue #344

[rui1610]

It should still be possible to allow additional sub account administrators. With the change in btp_cli.py this will be restricted to one person. This shouldn't be the case.

[lechnerc77]

It should still be possible to allow additional sub account administrators. With the change in btp_cli.py this will be restricted to one person. This shouldn't be the case.

@rui1610 : You can still assign the additional subaccount admins via the usecase.json like this:

{
    "$schema": "https://raw.githubusercontent.com/SAP-samples/btp-setup-automator/main/libs/btpsa-usecase.json",
    "aboutThisUseCase": {
        "name": "Default use case on how to show how btp-setup-automator works.",
        "description": "This usecase sets up services instances of (free) service plans on SAP BTP.",
        "author": "[email protected]",
        "testStatus": "tested successfully",
        "usageStatus": "READY TO BE USED"
    },
    "assignrolecollections": [
        {
            "name": "Subaccount Administrator",
            "type": "account",
            "level": "sub account",
            "assignedUserGroupsFromParameterFile": [
                "admins",
            ]
        },
        {
            "name": "OrgManager",
            "type": "cloudfoundry",
            "level": "org",
            "assignedUserGroupsFromParameterFile": [
                "owners"
            ]
        }
    ]
}

The parameters.json must contain information like this:

{
  "$schema": "https://raw.githubusercontent.com/SAP-samples/btp-setup-automator/main/libs/btpsa-parameters.json",
  "usecasefile": "usecases/released/default.json",
  "region": "us10",
  "globalaccount": "12334556",
  "myemail": "[email protected]",
  "loginmethod": "sso",
  "subaccountname": "test-roles",
  "myusergroups": [
    {
      "name": "admins",
      "members": [
        "[email protected]",
        "[email protected]"
      ]
    },
    {
      "name": "owners",
      "members": [
        "[email protected]",
        "[email protected]"
      ]
    }
  ]
}