maintain-simple_gh_aws_creds-run-integration-test
Run the integration test of simple_gh_aws_creds against the real AWS account and this GitHub repository, as done before each release: CLI setup and rotate_key through mise exec, a local check of each
SKILL.md.claude/skills/maintain-simple_gh_aws_creds-run-integration-test/SKILL.md
GitHubProve that the working tree's CLI works against the real AWS and GitHub APIs, using the committed config .github/simple_gh_aws_creds.json and workflow .github/workflows/test-aws-creds.yml. Run before each release.
Read ../maintain-simple_gh_aws_creds-base/SKILL.md, then:
- ../maintain-simple_gh_aws_creds-base/references/05-known-traps.md
- ../maintain-simple_gh_aws_creds-base/references/06-integration-test.md
Steps
Follow the routine in 06-integration-test.md section 6:
- Check the ground. Run
mise run cov; stop if it fails. Check the AWS profile read-only (aws sts get-caller-identity --profile bmt_app_dev_us_east_1, or the boto3 equivalent). Say which IAM user, account, and repository the test touches. setup, after the user's yes, with the command in06-integration-test.mdsection 3. Report each step's result line; never print the key file.- Check the key locally with the script in
06-integration-test.mdsection 4. Read-only, so it needs no yes. Expected: own user allowed,list usersdenied. - Run the workflow, after the user's yes, with the commands in
06-integration-test.mdsection 5. Report the conclusion and the run URL. If it fails right after step 2, re-run once for IAM propagation before debugging. rotate_key --yes, after the user's yes. Then repeat step 3 (no yes needed) and step 4 (after its own yes), to prove the new key reached GitHub.teardownonly on request. It is not part of the routine. Show the preview without--yesfirst, check the secret names against05-known-traps.mdsection 2, and runteardown --yesonly after the user's yes.
A step that fails stops the test: report the error, and fix the code before re-running.
Report
The commands run, each step's outcome (with masked key IDs only), each workflow run's URL and conclusion, and what was left in place (the IAM user, the current key, the secrets, the local key file).
Next step: pywf-oss-release if the test ran before a release; pywf-oss-changelog first if code changed to make it pass.