fix(integration): quote the Security & access menu in the Logfire prompts - #90
Open
nwm-54 wants to merge 1 commit into
Open
fix(integration): quote the Security & access menu in the Logfire prompts#90nwm-54 wants to merge 1 commit into
nwm-54 wants to merge 1 commit into
Conversation
…mpts Logfire's dashboard has no "API keys" menu; both the project and the organization settings expose keys under "Security & access". The project key also needs "Manage project and org" ticked alongside "Read-only access", or the data plane rejects it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #88. Logfire's dashboard has no "API keys" menu: both project settings and organization settings expose keys under Security & access, and the project key also needs Manage project and org ticked alongside Read-only access, or the data plane rejects it. The two prompts and the picker hint now quote those labels; the console copy in coreplanelabs/nominal is being corrected the same way.
Verification against the live production spec:
npm run codegen,tsc --noEmit,npm run lint, andnpm test(460/460) all clean;dist/polylane.mjs integration connect --type logfire --non-interactivestill exits 2 naming--api-key.🤖 Generated with Claude Code