Skip to content

Split function admin API key into staging and production - #2

Open
m-messer wants to merge 1 commit into
mainfrom
split-function-admin-api-key
Open

m-messer wants to merge 1 commit into
mainfrom
split-function-admin-api-key

Conversation

@m-messer

Copy link
Copy Markdown
Member

Replaces the shared function-admin-api-key with environment-specific keys for Lambda deploys, the same change as lambda-feedback/evaluation-function-workflows#14.

  • deploy.yml accepts function-admin-api-key-staging and function-admin-api-key-production. Staging deploys use the staging key and production deploys use the production key when they call lambda_deploy.yml.
  • function-admin-api-key stays as a deprecated fallback, so callers that haven't been updated keep working. A run that passes it shows a deprecation warning.

Merge this before the matching PRs in the chat function repos. Those repos pass the new secret names, which the current main rejects.

🤖 Generated with Claude Code

Add function-admin-api-key-staging and function-admin-api-key-production
secrets for Lambda deploys, keeping function-admin-api-key as a
deprecated fallback so existing callers keep working.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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