refresh content from any environment

Author: kurowski

README.md

@@ -17,6 +17,8 @@ To see a list of available commands, run `uceap` in the terminal. You can also r
 
 I frequently invoke `uceap refresh-content` to reset my local environment after switching branches. It runs `composer install` and invokes `db-rebuild.sh` with a fresh copy of the latest snapshot of the dev environment database and files. With shell completions installed, it's as easy as `uce<TAB>r<TAB>`.
 
+Troubleshooting an issue on the live site? `TERMINUS_ENV=live uceap refresh-content` will pull the latest backup of the database and files from LIVE. _You'll be knee-deep in PII in no time!_ **Be sure to reset your database and files with DEV data as soon as you're done.**
+
 > 👉 When working on a PR that adds update hooks or makes config changes, it's generally a good idea to make sure it applies cleanly to a database matching the QA environment. To do this, switch to the `qa` branch, run refresh-content, switch back to your branch, and run the deploy command (e.g. `drush md` for the portal):
 > ``` zsh
 > git checkout qa

local/etc/uceap.d/refresh_content.sh

@@ -4,7 +4,7 @@ function refresh_content() {
 	composer compile-theme
 
 	# download pantheon backups
-	export TERMINUS_ENV="dev"
+	export TERMINUS_ENV=${TERMINUS_ENV:-"dev"}
 	FILES_BACKUP=$(mktemp --dry-run files-XXXXXX.tar.gz)
 	DATABASE_BACKUP=$(mktemp --dry-run database-XXXXXX.sql.gz)
 	terminus backup:get --element=files --to=$FILES_BACKUP
@@ -33,17 +33,20 @@ Refreshes local code, files, and database in devcontainer.
 
 ``` bash
 uceap refresh-content
+TERMINUS_ENV=live uceap refresh-content
 ```
 
+## Options
+
+This command defaults to using the DEV environment. You can override this by setting the `TERMINUS_ENV` environment variable.
+
 ## Description
 
 This command is useful when switching branches.
 
-First it runs composer install, in case the new branch has updated dependencies.
-
-It also compiles the theme, in case there are any changes to the theme between branches.
+First it runs composer install, in case the new branch has updated dependencies. It also compiles the theme, in case there are any changes to the theme between branches.
 
-Then it downloads the latest backups from DEV and replaces the local files and database with them.
+Then it downloads the latest backups from Pantheon and replaces the local files and database with them.
 
 Finally, it rebuilds the database using the new database backup.
 '