Skip to content

Check that Neon key saving rejects org keys - #18

Merged
raghubetina merged 2 commits into
mainfrom
drawing-board-neon-key-check
Oct 6, 2026
Merged

raghubetina merged 2 commits into
mainfrom
drawing-board-neon-key-check

Conversation

@raghubetina

Copy link
Copy Markdown
Contributor

The fake neonctl now answers profile list --output json and me --output json from the key it saved, so the workshop helper check covers an organization key (save prints INVALID, keeps the form, check names the wrong kind) and a personal key (SAVED, check passes). Qualifies firstdraft/drawing-board#78 at a87160456bffdd6e76551ff23cff492e6d556159.

The Board's neon-key.sh save now runs auth.sh check neon, which asks
neonctl profile list for the saved credential and then neonctl me.
neonctl 8 saves an organization or project key, but me answers
"not allowed for organization API keys", so attendees who made one
failed later with a vague message. The fake neonctl now keeps the
saved key and answers both commands, so the check covers an
organization key that save rejects and keeps the form for, then a
personal key that saves and passes.
The Board's check_neon and neon-key.sh save now ask neonctl which
credential it will use and reject organization and project keys,
which the updated workshop helper check exercises.
@raghubetina
raghubetina merged commit 70e6d6d into main Oct 6, 2026
1 check passed
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.

1 participant