With the existing code you get these columns:
labels.cloudidentity.googleapis.com/groups.discussion_forum,labels.cloudidentity.googleapis.com/groups.security
but there is no data in the columns so you can't tell whcih groups have which values; by translating '' to True you can.
* Add view all|company|personal to print devices
Update documentation
* sync devices cleanup
* Update sync devices documentation
* Cleanup;
The advantage here is that they will be no filter errors unless you specify a particular view and a filter that doesn't match
* Simplify selection of devices to print
Default - all
Positve choices
Negative choices - backwards compatible
* Device updates
Make info device consistent with action device: id keyword is optional
Add nodeviceusers to print devices
pylint cleanup
* Fix documentation
* Sdd orderby to print devices
* Device assetTag cleanup
* Fix typo, appease pylint
* Strip C from customer ID
* userKey and customer is an invalid combination; userkey and domain is allowed
* DASA suggestions
I would not use OAUTHFILE to distinguish between normal/DASA, it seems to me that this might lead to oauth2service.json getting deleted by accident.
By using enabledasa.txt you can flip between the two modes easily.
* Update __init__.py
Is this what yuou meant?
Google now allows GCP service accounts to be granted delegated admin status for a G Suite domain.
To use this, admins can grant the service account email address delegated admin rights in the admin console
and then set some environment variables for GAM to use:
OAUTHFILE=oauth2service.json
GA_DOMAIN=example.com # your primary domain name in Google
CUSTOMER_ID=1d80dfc # admin.google.com > Account > Account settings > Customer ID
