Lezeh

lezeh is a CLI tool to ease day-to-day engineering operations such as: * Cherry pick database row and its relations * Visualize graph representation of a database row relations * Merging feature branch (by convention, specific using phabricator task number) into master, this includes cleaning up (delete) the merged feature branch * Merge and run deployment commands

Install

Download binaries

Go to latest releases and download the binaries here

| Binary | OS | | ------------------------------------ | ----- | | lezeh-x86_64-unknown-linux-gnu.zip | Linux | | lezeh-x86_64-apple-darwin.zip | macOS |

Using cargo

bash cargo install lezeh

Building manually

This requires rust bash make install

Setup

First create config file at ~/.lezeh, we're using YAML format. Each top level key is named after lezeh sub command: * url maps to lezeh url ... command * db maps to lezeh db ... sub command * and so on...

```yaml url: bitly: api_token: test123

db: dbconnectionbyname: testdb: host: localhost port: 5432 database: dbname username: .... password: ....

deployment: phab: apitoken: test125 pkcs12path: /path/to/pkcs12 host: 'yourphabricatorhost.com' pkcs12_password: abcdefg

ghub: api_token: test124

repositories: # This is a unique key that will be used as hashmap key # for the repo. - key: "repo-key" path: "repo-local-path" githubpath: "username/reponame" deploymentschemebykey: stg: name: "Deploy to stg" defaultpullrequesttitle: "Merge into stg" mergefrombranch: "master" mergeintobranch: "stg" prod: name: "Deploy to prod" defaultpullrequesttitle: "Merge into prod" mergefrombranch: "stg" mergeintobranch: "prod" ```

Usage

URL cli

lezeh url shorten {longUrl}

Database cli

Mostly tooling related with database operations. Only supports postgres as of now.

cherry-pick

Imagine you have this 1 table row that you want to copy but you can't easily copy it because it has relations and you need to copy the parents and children recursively. This is where cherry-pick can be useful.

```bash lezeh db cherry-pick \ # Fetch from test_db, this one is based on the config --source-db=testdb \

# As of now only supports 1 value, but it will change in the future --values=123 \

# Table that the value will be fetched from --table=orders \

# [Optional] which column that contains the given values, defaults to id --column=id \

# [Optional] Db schema, defaults to public --schema=public \

# [Optional], defaults to insert-statement. If supplied Graphviz then it'll serialize # the graph representation that can be represented in a graphviz format # see https://graphviz.org/ for more details. # The output can be used on online graphviz visualizer: # * https://edotor.net # * https://dreampuf.github.io/GraphvizOnline --output-format=insert-statement|graphviz \

# [Optional] # The option will be used if you choose pass --output-format=graphviz. # Set the table columns that will be displayed on each node, if not set it'll # default to only show the row id, format: # '{table1}:{column1}|{column2}|{columnn},{tablen}:{columnn}' # # Suppose you pass --graph-table-columns='users:id|name|email, orders:code', it will # * Show id, name and email column value for all fetched rows from users table # * Show code column value for all fetched rows from orders table # * The other rows from other tables will still only show row id because # it's not overriden --graph-table-columns='{table1}:{column1}|{column2}|{columnn},{tablen}:{columnn}, {tablen}:{columnn}' ```

Deployment cli

```bash

Below command will iterate all repositories under deployment.repositories config

and do the following operations:

* Make sure your local git data is updated by pulling remote git data from GH.

* For each remote branches that contains the given task numbers:

- Print out phabricator task owner (assigned) for that specific branch.

- Create a PR for the matched branch.

- Merge the branch into master with SQUASH strategy

- Delete the remote branch

lezeh deployment merge-feature-branches {tasknumber} {tasknumber} {task_number} ...

Merge repo (given repo key) based on given deployment scheme config.

#

Example usage (based on above config example):

lezeh deployment deploy repo-key stg

lezeh deployment deploy {repokey} {schemekey} ```