- Programmatically set Consent (Branding page) saving a user step
- record created_by in client_secrets.json for easier backtracking
- use local project-apis.txt if it exists
* Improve error handling when invalid report is entered
* Add chat to report list
* Use discovery document
* This will work
* Fix formatting
* These aren't necessary
* Yes, these are necessary because the user may enter the version without _ and gam has has to add it back
* f string formatting, final of many
Standardize (i/count) handling
Add doc_string and follow PEP8 naming convention for page_message routines
* Clean up items in gapi.got_total_items_msg and gapi.got_total_items_first_last_msg
* Allow : in row filter field names
export GAM_CSV_ROW_FILTER="'\"accounts:used_quota_in_mb\":count>=15000'"
* Updated code to handle Directory API issue that prevents looking up the orgUnitId of OU /
This affected `gam report` if you used the `orgunit /` option.
This affected `gam create admin <UserItem> <RoleItem> org_unit /`.
* Move transport customizations to their own module
This helps to accomplish a few things:
1) Makes the forced user-agent customization on HTTP requests a bit
clearer by subclassing the targeted objects (as opposed to hiding the
behavior behind a forced override of the google_auth_httplib2 object
methods)
2) Standardizes the creation of HTTP objects. These objects can still
largely be customized, but using a single creation mechanism will
standardize a default and streamline creation, thereby decreasing the
code that would otherwise be replicated in the caller
3) Moves create_http() to a more general purpose module, since it will
likely be used by more than gapi-related methods.
* Use string values for TLS version tests
More closely matches [existing
behavior](4fb73e6073/src/var.py (L853))
that sets the global default to a string value.
Requires use of a context manager within each test method for stdout/stderr patches, rather than the @patch.object decorator. Otherwise, the test runner hijacks the patched object before the method under test can use it.
Note: The `--buffer` switch in the unittest module will suppress all
output during the test, unless the test fails. However, with this implementation, anything that would have been printed to the streams within
the context manager will not be reflected in the test runner's output,
should the test fail.
See more in jay0lee/GAM#1068
