fnox set ignores existing key name when using remote provider
#711
Unanswered
twelvelabs
asked this question in
Troubleshooting and Bugs
Replies: 1 comment
|
Confirmed—thanks for the detailed report. I opened #712 to preserve the existing key when the selected provider matches. AI-assisted — Tool: Codex; model: openai/gpt-5; version: unavailable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Given the following
fnox.toml:Running
fnox set MY_SECRET somethingresults in updating the config to:And creating
MY_SECRETin Google Secret Manager (rather than the expectedcustom-secret-name):$ gcloud secrets list --project my-gcp-project NAME CREATED REPLICATION_POLICY LOCATIONS MY_SECRET 2026-08-12T20:22:28 automatic -I see that
fnox set --key-name=custom-secret-name MY_SECRET somethingworks as expected, but I would expect that the config value would be respected if the--key-nameflag was not provided.If I'm understanding things correctly, it looks like this is where the key name is resolved:
fnox/src/commands/set.rs
Lines 168 to 179 in f978acc
Shouldn't it load
secret_configbefore that and usesecret_config.valuebefore falling back toself.key?All reactions