How should an API key for a custom provider be supplied?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- devops
Research direction
Start by reading the action inputs and how review.yml passes them to the Codex process. Trace how codex-config and codex-auth are handled, then check whether the action can expose workflow secrets as environment variables for env_key. Done means the intended credential practice is documented or supported with a clear, secure input path.
Written by the indexing model from the issue text.
Description
Question
The action takes two content inputs, codex-config (a config.toml) and codex-auth (an auth.json). For a custom provider that speaks the Responses API and authenticates with a static API key, neither is an obvious fit:
codex-configworks, but only by writing the key into[model_providers.<name>].experimental_bearer_token. The Codex config schema says that field is "discouraged in favor ofenv_keyfor security reasons, but this may be necessary when using this programmatically".codex-authis described as "to sign in with ChatGPT instead of an API key", and settingrequires_openai_auth = truewould make Codex treat the provider as an OpenAI account login rather than a custom endpoint.
env_key looks like the clean answer — the config names a variable, the workflow supplies it from secrets.* — but there is no path to export an environment variable into the action: review.yml exposes no such input, and a caller cannot attach env: to a jobs.<id>.uses: entry.
What I'm asking
Which of these is the intended practice today, and would you consider supporting the standard shape?
- Keep writing
experimental_bearer_tokenintocodex-config, as the accepted programmatic escape hatch. - Add an input such as
codex-env(newline-separatedKEY=VALUEpairs exported before Codex runs), so the config can useenv_keyand the secret never appears in the config text. - Something else entirely — e.g.
authcommand-backed credentials are meant for this.
Option 2 would let the config.toml live in the repository (or a repository variable, via codex-config-file) while the key stays a workflow secret only.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h
- Merged PRs (30d)
- 118
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from promplate/code-review
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
promplate/code-review#158 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in promplate/code-review
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Update project links after the repository renamesPossibly taken @JonathanTSilva claimed this today. Openai-generated priority: p2 size: xs type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
JonathanTSilva/jts-website#119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Docs] CONTRIBUTING points the Backend Remake milestone at a branch that does not existPossibly taken @franpts2 claimed this today. Opendocs
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day