Support SpeWall in bash variables

NOTE: consider migrating from GH private repo to Google's Git on Borg. This is
preferable since GH gets hacked and private repos can be exposed. While a path
to a Google 3 repo like SpeWall may not pose a large security risk, it certainly
isn't optimal. Imagine a path to a repository whose name leaked a secret
project. Two options:

1. embrace encryption options like Mozilla's `sops` and remain on GH private
2. switch wholesale from private GH to GoB
3. classify "sensitve" parts of dotfiles as such and move those to GoB and keep
   everything else on private GH

One added perk of switching to GoB is saving the $7 monthly fee to support
private GH repos.
This commit is contained in:
William Carroll 2019-03-27 18:28:59 +00:00
parent 79387acb96
commit 97c156be88

View file

@ -21,6 +21,11 @@ hash -d escalations=./corp/gtech/pto/tda/beacons_extension
hash -d ultra=./ads/doubleclick/systems/crm
hash -d incentives_fe=./experimental/adservices/jarvis/jarvis_extension/jarvis_staging/js
hash -d incentives_be=./experimental/adservices/tesseract/handlers/incentives
hash -d spewall_fe=./alkali/apps/speakeasydashboard
hash -d spewall_be=./alkali/apps/speakeasydashboard
hash -d spewall_be=./java/com/google/alkali/applications/speakeasydashboard
hash -d spewall_protos=./google/internal/alkali/applications/speakeasydashboard
hash -d spewall_tests=./javatests/com/google/alkali/applications/speakeasydashboard
# 8-bit colors
black='\u001b[30m'