scrape-zyte-login

API keys must never appear in the transcript. Do not echo, read, or write key values directly.

SHUB_APIKEY and ZYTE_API_KEY are persisted in the project's .env file. Keep .env out of version control.

1. Check credentials

Report whether each key is set in the environment or stored in .env (do not export anything):

{ [ -n "$ZYTE_API_KEY" ] || grep -q '^ZYTE_API_KEY=' .env 2>/dev/null; } && echo "ZYTE_API_KEY: present" || echo "ZYTE_API_KEY: missing"
{ [ -n "$SHUB_APIKEY" ] || grep -q '^SHUB_APIKEY=' .env 2>/dev/null; } && echo "SHUB_APIKEY: present" || echo "SHUB_APIKEY: missing"

If both are present, proceed to step 3.

2. Run OAuth setup flow

Tell the user: