Repository navigation
docs: replace dead trello.com/app-key credential flow - #118
Open
piggyatbaqaqi wants to merge 1 commit into
Open
piggyatbaqaqi wants to merge 1 commit into
piggyatbaqaqi wants to merge 1 commit into
Conversation
trello.com/app-key no longer issues standalone API keys; it redirects to the Power-Up admin. Following the old instructions dead-ends, and the recovery path is not discoverable: a Power-Up must be created first, its "Iframe connector URL" field looks mandatory (it is not, and suggests you need to host something publicly), and the "Secret" shown beside the API key is easily mistaken for TRELLO_TOKEN. Both are 64 lowercase hex characters, but the Secret is the OAuth 1.0 client secret and fails authentication when used as a token. Document the current flow in README, and correct the stale links in .env.template and example.env. example.env already carried the right /1/authorize URL for the token; only its API key link was wrong. Docs only; no behaviour change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This branch has not been deployed
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
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.
Problem
trello.com/app-keyno longer issues standalone API keys — it redirects to the Power-Up admin. The README,.env.template, andexample.envall still point there, so new users following the setup instructions dead-end on the very first step.The recovery path isn't self-evident either. I hit all three of these getting the server running:
invalid keyfrom the API.Changes
#### Getting your API key and tokensection with the current five-step flow, an explicit note that the Iframe connector URL can be left blank, and a callout distinguishing the Secret from the token. The install section now links to it instead of repeating instructions./1/authorizeURL for the token; only the key link was wrong.Docs only, no behaviour change.
tsc --noEmitpasses.Notes
Verified end to end against a live board: created a Power-Up with a blank iframe URL, generated a key and token by these exact steps, and confirmed the server connects and its tools work (
add_commentandupdate_card_detailsboth exercised over stdio).One incidental finding, not addressed here:
CONTRIBUTING.mdstep 5 says to runnpm run lint, but there's nolintscript inpackage.json. Happy to open a separate PR if you'd like it added or the instruction dropped.Disclosure
This change was written with AI assistance (Claude, via Claude Code), directed and reviewed by me. The commit carries a
Co-Authored-By:trailer to that effect. I'm flagging it here as well so it's visible up front rather than only in the git metadata — happy to adjust the attribution to whatever form you prefer for this project.