feat: k6 prod post-deploy testing with pre-funded accounts (CPL-178)#258
Merged
feat: k6 prod post-deploy testing with pre-funded accounts (CPL-178)#258
Conversation
…L-178) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
The job-level env var was renamed from ACCOUNTS_FILE to K6_ACCOUNTS_FILE, but the step-level fallback expressions still referenced env.ACCOUNTS_FILE. This caused staging/dev runs (without the accounts_json secret) to resolve to an empty string instead of the branch-appropriate accounts file. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Hardcode api_root_url and attestation_url instead of reading from deploy-context.json, consistent with the other jobs in this workflow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace hardcoded api.chipotle.litprotocol.com with the DOMAIN_PROD GitHub repository variable for DRY configuration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…rkflow Updated the input name and all callers (deploy-prod-2-execute, deploy-staging). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Renamed 5 workflow files that are triggered exclusively via workflow_dispatch to make their manual nature clear from the filename: - contract-upgrade-prod-1-propose.yml - contract-upgrade-prod-2-verify.yml - contract-upgrade.yml - deploy-prod-2-execute.yml - k6-prod-test.yml Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…aming Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
K6_ACCOUNTS_PROD_JSONGitHub secretK6_ENV=prod) sincepm_card_visadoesn't work with live keysk6-prod-test.ymlworkflow for manually running the prod test suite without triggering a deploymentdeploy-prod-2-execute.ymlso tests run automatically after prod deploysNETWORK=prodsupport to the k6 justfilePre-requisite
Create and fund account(s) on prod, then store the JSON as GitHub secret
K6_ACCOUNTS_PROD_JSONin format:{"accounts": [{"apiKey": "...", "walletAddress": "...", "usageApiKey": "..."}]}Test plan
K6_ACCOUNTS_PROD_JSONsecret in GitHubdeploy-prod-2-execute) passes k6 tests with pre-funded accounts🤖 Generated with Claude Code