Operator should not target locally targeted resource group when using API Key

[jzaccone]

When using an API Key/Service ID, there should be away to specify the target resource group that the operator uses. Right now it uses the locally defined targeted operator, which may or may not be the same resource group as the API Key.

John_Zaccone@cloudshell:~$ ibmcloud target -g remkohdev-liab-test-group
Targeted resource group remkohdev-liab-test-group
                      
API endpoint:      https://cloud.ibm.com   
Region:            us-south   
User:              [email protected]   
Account:           IBM Client Developer Advocacy (e65910fa61ce9072d64902d03f3d4774) <-> 2058850   
Resource group:    remkohdev-liab-test-group   
CF API endpoint:      
Org:                  
Space:      
          
John_Zaccone@cloudshell:~$ curl -sL https://raw.githubusercontent.com/IBM/cloud-operators/master/hack/configure-operator.sh | bash -s -- install
secret/ibmcloud-operator-secret unchanged
configmap/ibmcloud-operator-defaults configured
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 29139  100 29139    0     0  96486      0 --:--:-- --:--:-- --:--:-- 96486
Downloaded:
...

John_Zaccone@cloudshell:~$ kubectl get configmap/ibmcloud-operator-defaults -o yaml | grep resource
  resourcegroup: remkohdev-liab-test-group
  resourcegroupid: c47309f3ea86467996541820af87361f
      {"apiVersion":"v1","data":{"org":"","region":"us-south","resourcegroup":"remkohdev-liab-test-group","resourcegroupid":"c47309f3ea86467996541820af87361f","space":"","user":"[email protected]"},"kind":"ConfigMap","metadata":{"annotations":{},"labels":{"app.kubernetes.io/name":"ibmcloud-operator"},"name":"ibmcloud-operator-defaults","namespace":"default"}}
        f:resourcegroup: {}
        f:resourcegroupid: {}
  resourceVersion: "677918"

[jzaccone]

I found the instructions to manually change the configmap to point to a new account/resource group. But perhaps a more explicit operator configuration should be considered here. (or at least a prompt in the installation script)