Skip to content

feature(CI): Simplify test workflow to always use production API key - #1

Merged
szemyd merged 1 commit into
mainfrom
claude/bump-flow-client-factors-test-2c8m05
Jul 25, 2026
Merged

szemyd merged 1 commit into
mainfrom
claude/bump-flow-client-factors-test-2c8m05

Conversation

@szemyd

@szemyd szemyd commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Updated the test workflow to always use the production API key regardless of the target environment, while maintaining separate Cloudflare Access credentials for non-production deployments.

Key Changes

  • Removed conditional logic that selected staging API key for non-production environments
  • Simplified APERIODIC_API_KEY environment variable to always use the production secret
  • Updated workflow input description to clarify that production API key is used in all cases
  • Cloudflare Access credentials remain conditionally set only for non-production deployments

Implementation Details

The change reflects a shift in credential management strategy where:

  • The production API key is now the single source of truth for all test runs
  • Non-production environments (staging, preview) still receive appropriate Cloudflare Access credentials for authentication
  • This simplification reduces credential complexity while maintaining proper access control for different deployment targets

https://claude.ai/code/session_01SF8uEam7rXgJWppNpEbr3v

Drop the separate staging API key. Staging and preview runs use the
production API key and additionally send Cloudflare Access credentials.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SF8uEam7rXgJWppNpEbr3v
@szemyd szemyd changed the title Simplify test workflow to always use production API key feature(CI): Simplify test workflow to always use production API key Jul 25, 2026
@szemyd
szemyd merged commit 9a902e4 into main Jul 25, 2026
11 checks passed
@szemyd
szemyd deleted the claude/bump-flow-client-factors-test-2c8m05 branch July 25, 2026 13: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.

2 participants