Enhanced Amplify secret detection

- Check multiple possible locations for the API key
- Add debugging to find available environment variables
- Try secrets object, AMPLIFY_ prefix, and standard env var
- Create placeholder .env.production file

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Derek Slenk 2025-06-27 15:24:46 -04:00
parent 627da2c7ec
commit 2de4fb5f69

View file

@ -5,18 +5,32 @@ frontend:
commands:
- npm ci
- echo "Checking for environment variables..."
- printenv | grep YOUTUBE || echo "No YOUTUBE env vars found"
- echo "YOUTUBE_API_KEY value length:" $(echo -n "$YOUTUBE_API_KEY" | wc -c)
- printenv | grep -E "(YOUTUBE|_SECRET)" || echo "No relevant env vars found"
- |
# Check if secrets are available through Amplify's secret mechanism
if [ ! -z "$secrets" ]; then
echo "Secrets object found"
echo "$secrets" | jq '.' 2>/dev/null || echo "Could not parse secrets"
fi
build:
commands:
- |
# Try multiple ways to access the secret
if [ ! -z "$YOUTUBE_API_KEY" ]; then
echo "Found YOUTUBE_API_KEY in environment"
echo "YOUTUBE_API_KEY=$YOUTUBE_API_KEY" >> .env.production
echo "Created .env.production with YOUTUBE_API_KEY"
elif [ ! -z "$secrets" ] && [ ! -z "$(echo $secrets | jq -r '.YOUTUBE_API_KEY' 2>/dev/null)" ]; then
echo "Found YOUTUBE_API_KEY in secrets object"
echo "YOUTUBE_API_KEY=$(echo $secrets | jq -r '.YOUTUBE_API_KEY')" >> .env.production
elif [ ! -z "$AMPLIFY_YOUTUBE_API_KEY" ]; then
echo "Found AMPLIFY_YOUTUBE_API_KEY in environment"
echo "YOUTUBE_API_KEY=$AMPLIFY_YOUTUBE_API_KEY" >> .env.production
else
echo "WARNING: YOUTUBE_API_KEY is not set in environment"
echo "WARNING: YOUTUBE_API_KEY not found in any expected location"
echo "Available env vars starting with A:"
printenv | grep "^A" | head -10
fi
- cat .env.production 2>/dev/null || echo "No .env.production file"
- cat .env.production 2>/dev/null || echo "No .env.production file created"
- npm run build
artifacts:
baseDirectory: .next