docs: record Etsy production credential configuration - #70
Merged
Conversation
Etsy issued new bulk-edit-app developer credentials; configured as encrypted SECRET env vars on bulk-edit-prod-api and verified via live OAuth URL generation. Rate limit and scope defaults already matched code, so no PR- worthy change beyond docs. Records the mid-task regex bug (PowerShell Regex.Replace count-arg misuse) caught and fixed before trusting the deploy.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bulk-edit-appdeveloper credentials (Keystring + Shared Secret, 5 QPS / 5000 QPD); configured as encryptedSECRETenv vars onbulk-edit-prod-apiviadoctl apps update --spec(already applied to production prior to this PR — docs-only change).ETSY_API_REQUESTS_PER_SECOND/ETSY_API_DAILY_LIMIT/ETSY_SCOPESinapp/core/config.py) — no code change.[regex]::Replace(...,1)call misinterpreted its 4th arg asRegexOptions(not a match-count limiter), causing triple-duplicated env entries across the api service and both jobs. Caught before trusting the deploy, fixed with a YAML-aware Python pass, re-verified, redeployed.qvmj...fh33), no full Keystring, no Shared Secret anywhere.Test plan
deploy_on_push: true— no functional change expected, existing env already applied directly via doctl🤖 Generated with Claude Code
https://claude.ai/code/session_01QW88Si1uvjKcAkzqn6nh5Y