gazer 0.2.9

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 9be1f366962bba0ba3b9ff09f8da55be6918e03f
+  data.tar.gz: 031e2bbd695dc6f180f9de2287892f399da35023
+SHA512:
+  metadata.gz: 51c76b2379314a222103a59e2f0797c0aa0fc4dbd9ad9f11b844fa46bdbbb40063329d241ba3dec982740928021c297d046ffb3948d9119a4e0a3dbab03a1c48
+  data.tar.gz: 6fc85c7094d58a4bc3e54f1ac6d610a930d451689ff03f4cdc5e9cdb9eaa628e5cfc95668ef2ff4d8c80c3641dea92b0dfe1eeedffab9ddc3071c94eea44f57a

data/.gitignore

@@ -0,0 +1,15 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+
+*~
+*.swp
+*.json

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.ruby-version

@@ -0,0 +1 @@
+ruby-2.3.3

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3.3
+before_install: gem install bundler -v 1.16.1

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at deangelo@looker.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -0,0 +1,35 @@
+# The MIT License (MIT)
+
+# Copyright (c) 2018 Mike DeAngelo Looker Data Sciences, Inc.
+
+# Permission is hereby granted, free of charge, to any person obtaining a copy of
+# this software and associated documentation files (the "Software"), to deal in
+# the Software without restriction, including without limitation the rights to
+# use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+# the Software, and to permit persons to whom the Software is furnished to do so,
+# subject to the following conditions:
+
+# The above copyright notice and this permission notice shall be included in all
+# copies or substantial portions of the Software.
+
+# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+# FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+# COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+# IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+# CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+RUBY_VERSION = File.read(File.join(File.dirname(__FILE__), '.ruby-version')).split('-').last.chomp
+
+ruby '2.3.3', engine: 'ruby', engine_version: RUBY_VERSION
+
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in gzr.gemspec
+gemspec
+#gem 'looker-sdk', :git => 'git@github.com:looker/looker-sdk-ruby.git'
+#gem 'tty', :git => 'git@github.com:piotrmurach/tty.git'
+#gem 'tty-file', :git => 'git@github.com:piotrmurach/tty-file.git'
+

data/Gemfile.lock

@@ -0,0 +1,150 @@
+PATH
+  remote: .
+  specs:
+    gazer (0.2.9)
+      looker-sdk (~> 0.0.6)
+      netrc (~> 0.11.0)
+      pastel (~> 0.7.2)
+      thor (~> 0.20.0)
+      tty-reader (~> 0.3.0)
+      tty-table (~> 0.10.0)
+      tty-tree (~> 0.1.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.5.2)
+      public_suffix (>= 2.0.2, < 4.0)
+    diff-lcs (1.3)
+    equatable (0.5.0)
+    faraday (0.15.4)
+      multipart-post (>= 1.2, < 3)
+    hitimes (1.3.0)
+    kramdown (1.16.2)
+    looker-sdk (0.0.6)
+      faraday (>= 0.9.0, < 1.0)
+      sawyer (~> 0.8)
+    multipart-post (2.0.0)
+    necromancer (0.4.0)
+    netrc (0.11.0)
+    pastel (0.7.2)
+      equatable (~> 0.5.0)
+      tty-color (~> 0.4.0)
+    public_suffix (3.0.3)
+    rake (10.5.0)
+    rouge (3.1.1)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.0)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.0)
+    sawyer (0.8.1)
+      addressable (>= 2.3.5, < 2.6)
+      faraday (~> 0.8, < 1.0)
+    strings (0.1.3)
+      strings-ansi (~> 0.1.0)
+      unicode-display_width (~> 1.4.0)
+      unicode_utils (~> 1.4.0)
+    strings-ansi (0.1.0)
+    thor (0.20.0)
+    timers (4.1.2)
+      hitimes
+    tty (0.8.1)
+      bundler (~> 1.16, < 2.0)
+      equatable (~> 0.5.0)
+      pastel (~> 0.7.2)
+      thor (~> 0.20.0)
+      tty-color (~> 0.4.2)
+      tty-command (~> 0.8.0)
+      tty-config (~> 0.2.0)
+      tty-cursor (~> 0.5.0)
+      tty-editor (~> 0.4.0)
+      tty-file (~> 0.6.0)
+      tty-font (~> 0.2.0)
+      tty-markdown (~> 0.4.0)
+      tty-pager (~> 0.11.0)
+      tty-platform (~> 0.1.0)
+      tty-progressbar (~> 0.15.0)
+      tty-prompt (~> 0.16.1)
+      tty-screen (~> 0.6.4)
+      tty-spinner (~> 0.8.0)
+      tty-table (~> 0.10.0)
+      tty-tree (~> 0.1.0)
+      tty-which (~> 0.3.0)
+    tty-color (0.4.3)
+    tty-command (0.8.2)
+      pastel (~> 0.7.0)
+    tty-config (0.2.0)
+    tty-cursor (0.5.0)
+    tty-editor (0.4.0)
+      tty-prompt (~> 0.16.0)
+      tty-which (~> 0.3.0)
+    tty-file (0.6.0)
+      diff-lcs (~> 1.3.0)
+      pastel (~> 0.7.2)
+      tty-prompt (~> 0.16.1)
+    tty-font (0.2.0)
+    tty-markdown (0.4.0)
+      kramdown (~> 1.16.2)
+      pastel (~> 0.7.2)
+      rouge (~> 3.1.0)
+      strings (~> 0.1.0)
+      tty-color (~> 0.4.2)
+      tty-screen (~> 0.6.4)
+    tty-pager (0.11.0)
+      strings (~> 0.1.0)
+      tty-screen (~> 0.6.4)
+      tty-which (~> 0.3.0)
+    tty-platform (0.1.0)
+    tty-progressbar (0.15.1)
+      tty-cursor (~> 0.5.0)
+      tty-screen (~> 0.6.4)
+      unicode-display_width (~> 1.3)
+    tty-prompt (0.16.1)
+      necromancer (~> 0.4.0)
+      pastel (~> 0.7.0)
+      timers (~> 4.0)
+      tty-cursor (~> 0.5.0)
+      tty-reader (~> 0.3.0)
+    tty-reader (0.3.0)
+      tty-cursor (~> 0.5.0)
+      tty-screen (~> 0.6.4)
+      wisper (~> 2.0.0)
+    tty-screen (0.6.5)
+    tty-spinner (0.8.0)
+      tty-cursor (>= 0.5.0)
+    tty-table (0.10.0)
+      equatable (~> 0.5.0)
+      necromancer (~> 0.4.0)
+      pastel (~> 0.7.2)
+      strings (~> 0.1.0)
+      tty-screen (~> 0.6.4)
+    tty-tree (0.1.0)
+    tty-which (0.3.0)
+    unicode-display_width (1.4.0)
+    unicode_utils (1.4.0)
+    wisper (2.0.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  gazer!
+  rake (~> 10.0)
+  rspec (~> 3.0)
+  tty (~> 0.8)
+
+RUBY VERSION
+   ruby 2.3.3p222
+
+BUNDLED WITH
+   1.16.1

data/LICENSE.txt

@@ -0,0 +1,20 @@
+The MIT License (MIT)
+
+Copyright (c) 2018 Mike DeAngelo Looker Data Sciences, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,527 @@
+# Gazer - A Looker Content Utility
+
+Gazer can be used to navigate and manges Spaces, Looks, 
+and Dashboards via a simple command line tool.
+
+## Status and Support
+
+Gazer is **NOT** supported or warranteed by Looker in any way. Please do not contact Looker support
+for issues with Gazer. Issues can be logged via https://github.com/deangelo-llooker/gzr/issues 
+
+## Installation
+
+You can install this gem by simply typing:
+
+    $ gem install gazer
+
+Alternately you can follow the Development setup below, typing `bundle exec rake install` to install it
+locally
+
+## Usage
+
+Display help information...
+
+    $ gzr help
+
+### Storing Credentials
+Store login information by creating the file `~/.netrc` in your home directory with the api3 credentials
+
+```
+machine foo.bar.mycompany.com
+  login AbCdEfGhIjKlMnOp
+  password QrStUvWxYz1234567890
+```
+
+Make sure that the `~/.netrc` file has restricted permissions by running `chmod 600 ~/.netrc`.
+
+### Options that apply to many commands
+
+#### --su option
+
+The `--su` option can be used with a user id to run the command as another user. This options works
+with all commands. In order to use the `--su` option the user must provide admin credentials.
+
+For example...
+
+```
+$ gzr user me --su 1237 --host foo.bar.mycompany.com
++----+----------+---------+---------------------+
+|  id|first_name|last_name|email                |
++----+----------+---------+---------------------+
+|1237|Susan     |Gibson   |sgibson@mycompany.com|
++----+----------+---------+---------------------+
+````
+#### Suppressing Formatted Output
+
+Many commands provide tabular output. For tables the
+option `--plain` will suppress the table headers and format lines, making it easier to use tools
+like grep, awk, etc. to retrieve values from the output of these commands.
+
+#### CSV Output
+
+Many commands provide tabular output. For tables thehe option `--csv` will output tabular data in
+csv format. When combined with `--plain` the header will also be suppressed.
+
+### User Information
+
+The command `gzr user help` will show details about subcommands of the user command.
+
+#### user me
+
+Display information about the current user with the command `gzr user me`.
+
+```
+$ gzr user me --host foo.bar.mycompany.com
++----+----------+---------+--------------------+
+|  id|first_name|last_name|email               |
++----+----------+---------+--------------------+
+|1234|John      |Smith    |jsmith@mycompany.com|
++----+----------+---------+--------------------+
+```
+
+#### user ls
+
+Display information about all users with the command `gzr user ls`.
+
+```
+$ gzr user ls --host foo.bar.mycompany.com
++----+----------+---------+---------------------+
+|  id|first_name|last_name|email                |
++----+----------+---------+---------------------+
+|1234|John      |Smith    |jsmith@mycompany.com |
+|1235|Frank     |Jones    |fjones@mycompany.com |
+|1236|Bill      |Weld     |wweld@mycompany.com  |
+|1237|Susan     |Gibson   |sgibson@mycompany.com|
+|1238|Anna      |Grace    |agrace@mycompany.com |
+|1239|Mike      |Arthur   |marthur@mycompany.com|
++----+----------+---------+---------------------+
+```
+
+Different fields can be returned using the `--fields` option. For example the option
+`--fields id,first_name,last_name,email,personal_space_id,home_space_id`.
+
+### Group Information
+
+The command `gzr group help` will show details about subcommands of the group command.
+
+#### group ls
+
+The command `gzr group ls` will list the groups defined on a particular Looker instance.
+
+```
+gzr  group ls  --host foo.bar.mycompany.com
++--+------------------------------------+----------+---------------------+------------------+-----------------+
+|id|name                                |user_count|contains_current_user|externally_managed|external_group_id|
++--+------------------------------------+----------+---------------------+------------------+-----------------+
+| 4|Ecommerce Dashboard-only User       |         2|false                |                  |                 |
+| 5|Marketing                           |         3|false                |                  |                 |
+| 6|Developer (no deploy)               |         6|false                |                  |                 |
+| 9|dashboard_only                      |         7|false                |                  |                 |
+|24|Finance Team                        |         2|false                |                  |                 |
+|25|Marketing Team                      |         1|false                |                  |                 |
+|36|Embed Shared Group Engineering      |         0|false                |                  |Engineering      |
+|37|Embed Shared Group ecomm_only_users |         1|false                |                  |ecomm_only_users |
+|38|Embed Shared Group awesome_engineers|         1|false                |                  |awesome_engineers|
+|39|sub finance                         |         1|false                |                  |                 |
+|49|All Users                           |       570|true                 |true              |                 |
++--+------------------------------------+----------+---------------------+------------------+-----------------+
+```
+
+#### group member_groups
+
+The command `gzr group member_group GROUP_ID` will list the group that have been added as
+as members of the given group id.
+
+```
+$ gzr  group member_group 24  --host foo.bar.mycompany.com
++--+-----------+----------+---------------------+------------------+-----------------+
+|id|name       |user_count|contains_current_user|externally_managed|external_group_id|
++--+-----------+----------+---------------------+------------------+-----------------+
+|39|sub finance|         1|                     |                  |                 |
++--+-----------+----------+---------------------+------------------+-----------------+
+```
+
+#### group member_users
+
+The command `gzr group member_users GROUP_ID` will list the users that have been added as
+as members of the given group id.
+
+```
+$ gzr  group member_users 39  --host foo.bar.mycompany.com
++----+---------------------+---------+----------+-----------------+-------------+
+|  id|email                |last_name|first_name|personal_space_id|home_space_id|
++----+---------------------+---------+----------+-----------------+-------------+
+|1237|sgibson@mycompany.com|Gibson   |Susan     |              758|          758|
++----+---------------------+---------+----------+-----------------+-------------+
+```
+
+### Space Information
+
+The command `gzr space help` will show details about subcommands of the space command.
+
+#### space ls
+
+The command `gzr space ls` will list the contents of a space, including subspaces, looks, and dashboards.
+
+Without any arguments, the command will list the contents of the user's "home" space.
+
+```
+$ gzr space ls --host foo.bar.mycompany.com
++---------+---+------+---------+----------------------------+--------------+--------------------------------+
+|parent_id|id |  name|looks(id)|looks(title)                |dashboards(id)|dashboards(title)               |
++---------+---+------+---------+----------------------------+--------------+--------------------------------+
+|         |801|Shared|         |                            |              |                                |
+|         |801|Shared|857      |Daily Profit                |              |                                |
+|         |801|Shared|1479     |totals                      |              |                                |
+|         |801|Shared|1486     |Test look2                  |              |                                |
+|         |801|Shared|1509     |Aircraft Production by Year |              |                                |
+|         |801|Shared|         |                            |192           |Daily Profit Dashboard          |
+|         |801|Shared|         |                            |261           |New Test Dashboard              |
+|         |801|Shared|         |                            |383           |Sales Dashboard                 |
+|         |801|Shared|         |                            |463           |Customer Dashboard              |
++---------+---+------+---------+----------------------------+--------------+--------------------------------+
+```
+
+With the argument "~" the command will list the content of the calling user's "personal" space.
+
+```
+$ gzr space ls "~" --host foo.bar.mycompany.com
++---------+----+----------+---------+-----------------+--------------+-------------------------------------+
+|parent_id|id  |      name|looks(id)|looks(title)     |dashboards(id)|dashboards(title)                    |
++---------+----+----------+---------+-----------------+--------------+-------------------------------------+
+|      709|1132|John Smith|         |                 |              |                                     |
+|      709|1132|John Smith|1570     |test             |              |                                     |
+|      709|1132|John Smith|1726     |you can delete me|              |                                     |
+|      709|1132|John Smith|1737     |My First Look    |              |                                     |
+|      709|1132|John Smith|         |                 |410           |Indicator Dashboard                  |
+|      709|1132|John Smith|         |                 |413           |Accidents Dashboard 2011             |
++---------+----+----------+---------+-----------------+--------------+-------------------------------------+
+```
+
+With a simple numeric argument the command will list the content of the space with the given space id.
+
+```
+$ gzr space ls 103 --host foo.bar.mycompany.com
+```
+
+With a tilde plus a simple numeric argument the command will list the content of the personal space
+of the given user id.
+
+```
+$ gzr space ls "~1237" --host foo.bar.mycompany.com
+```
+
+The user can be identified by name as well.
+
+```
+$ gzr space ls "~Susan Gibson" --host foo.bar.mycompany.com
+```
+Finally, the space can be searched by name.
+
+```
+$ gzr space ls "Marketing" --host foo.bar.mycompany.com
+```
+
+#### space tree
+
+The command `gzr space tree` will display the child spaces, dashboards, and looks in a tree format.
+
+```
+$ gzr space tree "~" --host foo.bar.mycompany.com
+John Smith
+├── Trace Data
+│   ├── (l) All-Time Visits
+│   └── (l) Sessions by Week
+├── (l) test
+├── (l) you can delete me
+├── (l) My First Look
+├── (d) Indicator Dashboard
+└── (d) Indicator Dashboard 2011
+```
+
+The same arguments are accepted as by `space ls`.
+
+#### space cat
+
+The `space cat` command is used to output the json that describes the space.
+
+```
+$ gzr space cat 758 --host foo.bar.mycompany.com
+{
+  "id": 758,
+  "creator_id": 1237,
+  "name": "Susan Gibson",
+  "content_metadata_id": 734,
+  "is_personal": true,
+  "is_shared_root": false,
+  "is_users_root": false,
+  "is_personal_descendant": false,
+  "is_embed": false,
+  "is_embed_shared_root": false,
+  "is_embed_users_root": false,
+  "external_id": null,
+  "parent_id": 709,
+  "is_user_root": false,
+  "is_root": false,
+  "looks": [
+  ],
+  "dashboards": [
+  ],
+  "can": {
+    "index": true,
+    "show": true,
+    "create": true,
+    "see_admin_spaces": true,
+    "update": false,
+    "destroy": false,
+    "move_content": true,
+    "edit_content": true
+  }
+}
+```
+
+The output document can be very long. Usually one will use the switch `--dir DIRECTORY` to
+save to a file. The file will be named `Space_{SPACE_ID}_{SPACE_NAME}.json`.
+
+#### space export
+
+The `space export SPACE_ID` command is used to export a space and its subspaces, looks, and dashboards.
+The structure of spaces and subspaces will be mirrored in directories and subdirectories in the file system
+under the directory given by the `--dir DIRECTORY` switch. The directories will be named like
+`Space_{SPACE_ID}_{SPACE_NAME}` and the metadata for each space will be stored in a
+file with the name `Space_{SPACE_ID}_{SPACE_NAME}.json` within its corresponding directory.
+
+The JSON information for the Looks and Dashboards in a space are usually part of the space
+json data. When using the export command, this information would be redundant and so it is not
+included in the `Space_{SPACE_ID}_{SPACE_NAME}.json` file.
+
+Looks and Dashboards will be located in the space directories in files named like
+`Look_{LOOK_ID}_{LOOK_TITLE}.json` and `Dashboard_{DASHBOARD_ID}_{DASHBOARD_TITLE}.json`.
+
+```
+$ gzr space export 758 --host foo.bar.mycompany.com --dir .
+```
+
+One interesting use of exporting a space into a directory tree is that it can be placed under version control
+using a tool like git. In that way user defined content changes can be tracked over time, and older versions
+of content can be restored if desired.
+
+Alternately, the space can be exported into a `tar` style archive file with the switch `--tar FILENAME`.
+
+```
+$ gzr space export 758 --host foo.bar.mycompany.com --tar export.tar
+```
+
+That tar file can also be automatically compressed with `gzip` compression by using the switch
+`--tgz FILENAME`.
+
+```
+$ gzr space export 758 --host foo.bar.mycompany.com --tgz export.tar.gz
+```
+
+#### space rm
+
+The `space rm SPACE_ID` command is used to delete a space. If the space is not empty
+this command will refuse to perform the delete. By adding the `--force` switch the command
+will also delete the subspaces, looks, and dashboards contained in the space.
+
+```
+$ gzr space rm 758 --host foo.bar.mycompany.com --force
+```
+
+#### space create
+
+The `space create NAME PARENT_SPACE_ID` command is used to create a new subspace.
+
+```
+$ gzr space create "My New Space" 758 --host foo.bar.mycompany.com
+```
+
+### Look Information
+
+The command `gzr look help` will show details about subcommands of the look command.
+
+#### look cat
+
+The `look cat` command is used to output the json that describes the look.
+
+```
+$ gzr look cat 758 --host foo.bar.mycompany.com
+JSON data for look
+```
+
+The output document can be very long. Usually one will use the switch `--dir DIRECTORY` to
+save to a file. The file will be named `Look_{LOOK_ID}_{LOOK_TITLE}.json`.
+
+#### look rm
+
+The `look rm LOOK_ID` command is used to delete a look.
+
+```
+$ gzr look rm 758 --host foo.bar.mycompany.com
+```
+
+#### look import
+
+The `look import LOOK_FILE SPACE_ID` command is used to import a look from a file. If a look by the same
+name exists in that space then the `--force` switch must be used.
+
+Gazer will attempt to update the existing look of the same name, rather than create a new look. In
+that way the look id, schedules, permissions, etc. will be preserved.
+
+```
+$ gzr look import Path/To/Look_123_My\ Look.json 123 --host foo.bar.mycompany.com --force
+```
+
+### Dashboard Information
+
+The command `gzr dashboard help` will show details about subcommands of the dashboard command.
+
+#### dashboard cat
+
+The `dashboard cat` command is used to output the json that describes the dashboard.
+
+```
+$ gzr dashboard cat 192 --host foo.bar.mycompany.com
+JSON data for dashboard
+```
+
+The output document can be very long. Usually one will use the switch `--dir DIRECTORY` to
+save to a file. The file will be named `Dashboard_{DASHBOARD_ID}_{DASHBOARD_TITLE}.json`.
+
+#### dashboard rm
+
+The `dashboard rm DASHBOARD_ID` command is used to delete a dashboard.
+
+```
+$ gzr dashboard rm 192 --host foo.bar.mycompany.com
+```
+
+#### dashboard import
+
+The `dashboard import DASHBAORD_FILE SPACE_ID` command is used to import a dashboard and
+its associated looks from a file. If a dashbaord or look by the same
+name exists in that space then the `--force` switch must be used.
+
+Gazer will attempt to update the existing dashboard or look of the same name, rather than 
+create a new dashboard or look. In
+that way the id, schedules, permissions, etc. will be preserved.
+
+```
+$ gzr dashboard import Path/To/Dashboard_123_My\ Dash.json 123 --host foo.bar.mycompany.com --force
+```
+
+### Connection Information
+
+The command `gzr connection help` will show details about subcommands of the connection command.
+
+#### connection ls
+
+The command `gzr connection ls` will list the connections that have been defined in the Looker instance.
+
+```
+$ gzr connection ls --host foo.bar.mycompany.com
++-------------------------+---------------------+-----------------+----+--------------------------+-----------+
+|name                     |dialect.name         |host             |port|database                  |schema     |
++-------------------------+---------------------+-----------------+----+--------------------------+-----------+
+|thelook                  |mysql                |db1.mycompany.com|3306|demo_db                   |           |
+|faa                      |mysql                |db1.mycompany.com|3306|flightstats               |           |
+|video_store              |mysql                |db1.mycompany.com|3306|sakila                    |           |
+|looker                   |mysql                |                 |    |                          |           |
++-------------------------+---------------------+-----------------+----+--------------------------+-----------+
+```
+
+#### connection dialect
+
+The command `gzr connection dialect` will list the dialects that have been defined in the Looker instance.
+
+```
+$ gzr connection dialect --host foo.bar.mycompany.com
++---------------------+----------------------------------+
+|name                 |label                             |
++---------------------+----------------------------------+
+|mysql                |MySQL                             |
+|amazonaurora         |Amazon Aurora                     |
+|googlecloudsql       |Google Cloud SQL                  |
+|memsql               |MemSQL                            |
+|mariadb              |MariaDB                           |
+|clustrix             |Clustrix                          |
+|postgres             |PostgreSQL                        |
+|google_cloud_postgres|Google Cloud PostgreSQL           |
+|azure_postgres       |Azure PostgreSQL                  |
+|presto               |PrestoDB                          |
+|athena               |Amazon Athena                     |
+|qubole_presto        |Qubole Presto v0.157+             |
+|qubole_presto_v142   |Qubole Presto v0.142              |
+|xtremedata           |XtremeData                        |
+|redshift             |Amazon Redshift                   |
+|snowflake            |Snowflake                         |
+|greenplum            |Greenplum                         |
+|mssql_2008           |Microsoft SQL Server 2008+        |
+|msazuresql           |Microsoft Azure SQL Database      |
+|mssql                |Microsoft SQL Server 2005         |
+|mssqldw              |Microsoft Azure SQL Data Warehouse|
+|aster                |Aster Data                        |
+|vertica              |Vertica 7.1+                      |
+|vertica_v5           |Vertica 6                         |
+|bigquery             |Google BigQuery Legacy SQL        |
+|bigquery_standard_sql|Google BigQuery Standard SQL      |
+|spanner              |Google Cloud Spanner              |
+|db2                  |IBM DB2                           |
+|datavirtuality       |DataVirtuality                    |
+|dashdb               |IBM DashDB                        |
+|hana                 |SAP HANA                          |
+|oracle               |Oracle                            |
+|oracle_dwcs          |Oracle ADWC                       |
+|hive2                |Apache Hive2                      |
+|impala               |Cloudera Impala                   |
+|spark1_5             |Apache Spark 1.5+                 |
+|spark2_0             |Apache Spark 2.0                  |
+|teradata             |Teradata                          |
+|exasol               |Exasol                            |
+|denodo               |Denodo                            |
+|druid                |Druid                             |
+|netezza              |IBM Netezza                       |
+|dremio               |Dremio                            |
++---------------------+----------------------------------+
+```
+
+### Model Information
+
+The command `gzr model help` will show details about subcommands of the model command.
+
+#### model ls
+
+The command `gzr model ls` will list the models that have been defined in the Looker instance.
+
+```
+$ gzr model ls --host foo.bar.mycompany.com
++---------------------------------------------+---------------------------------------------+-------------------------+
+|name                                         |label                                        |project_name             |
++---------------------------------------------+---------------------------------------------+-------------------------+
+|faa                                          |Faa                                          |faa                      |
+|300_daily_active_users                       |300 Daily Active Users                       |lookml_design_patterns   |
+|001_hello_world                              |001 Hello World                              |lookml_design_patterns   |
+|video_store                                  |Video Store                                  |video_store              |
+|looker                                       |Looker                                       |i__looker_dev            |
+|faa_redshift                                 |Faa Redshift                                 |faa_redshift             |
++---------------------------------------------+---------------------------------------------+-------------------------+
+```
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/deangelo-llooker/gzr. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## Code of Conduct
+
+Everyone interacting in the Gazer project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/deangelo-llooker/gzr/blob/master/CODE_OF_CONDUCT.md).
+
+## Copyright
+
+Copyright (c) 2018 Mike DeAngelo for Looker Data Sciences. See [MIT License](LICENSE.txt) for further details.