Skip to content

SNOW-4387808 Rotate the sfctest0 E2E key in profile.json - #1180

Merged
sfc-gh-aschuck merged 1 commit into
masterfrom
aschuck/SNOW-4387808-rotate-e2e-secrets
Nov 17, 2026
Merged

sfc-gh-aschuck merged 1 commit into
masterfrom
aschuck/SNOW-4387808-rotate-e2e-secrets

Conversation

@sfc-gh-aschuck

@sfc-gh-aschuck sfc-gh-aschuck commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Caution

Do not merge yet. This is part of a coordinated credential rotation (internal ticket SNOW-4387808). It must merge
on the scheduled switch-over day, before the old key is removed from the test user.

What

Updates profile.json.gpg (the AWS E2E profile) with a new private key for the E2E test user
snowpipe_sdk_gh_action on sfctest0.

  • Only the private_key value changed. Every other field is identical.
  • Still encrypted with this repo's existing PROFILE_JSON_DECRYPT_PASSPHRASE, which is not changing, so no
    secret update is needed here.
  • profile_azure.json.gpg and profile_gcp.json.gpg use a different user and key and are not affected.

Why

The credentials for this test user are being rotated as part of an internal security task. This repo's E2E logs
in as the same user, so its copy of the key has to be updated too.

How it's sequenced

  1. Done: the new public key was added to the user's second key slot (RSA_PUBLIC_KEY_2). The user
    currently accepts both the old and new keys, so master keeps working.
  2. Switch-over day: merge this PR. E2E on master then uses the new key.
  3. After E2E passes on the new key: the old key is removed from the user. From then on, only the new key in
    this file works. If this PR hasn't merged by then, E2E here fails to log in.

Rollback: until step 3, reverting this PR is enough. The old key still works.

Testing

  • The new key was checked to log in to sfctest0 as snowpipe_sdk_gh_action.
  • E2E on this PR, if it runs, logs in with the new key and is a direct check of this change.

🤖 Generated with Claude Code

Co-Authored-By: Claude Code <noreply@anthropic.com>
@sfc-gh-aschuck
sfc-gh-aschuck marked this pull request as ready for review November 17, 2026 18:24
@sfc-gh-aschuck
sfc-gh-aschuck requested review from a team as code owners November 17, 2026 18:24
@codecov-commenter

codecov-commenter commented Nov 17, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.60%. Comparing base (5abfa1a) to head (ba488ac).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1180      +/-   ##
==========================================
+ Coverage   58.98%   61.60%   +2.62%     
==========================================
  Files         214      214              
  Lines       14674    14674              
  Branches     1614     1614              
==========================================
+ Hits         8655     9040     +385     
+ Misses       5375     4921     -454     
- Partials      644      713      +69     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sfc-gh-aschuck
sfc-gh-aschuck merged commit f5d4f8d into master Nov 17, 2026
50 of 51 checks passed
@sfc-gh-aschuck
sfc-gh-aschuck deleted the aschuck/SNOW-4387808-rotate-e2e-secrets branch November 17, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants