CLI importer fails to authenticate
guillaumekh opened this issue · comments
Description
CLI importer fails to authenticate w/ Linear API when invoked w/ personal API key
Context
Broadcom/VMware/Pivotal have removed all non-entreprise pricing tiers for Pivotal Tracker with a 56 days notice, which should force whatever users they still had left to flee to other solutions (e.g. Linear).
Steps to reproduce
cat << EOF | tee test.csv
Id,Title,Labels,Iteration,Iteration Start,Iteration End,Type,Estimate,Priority,Current State,Created at,Accepted at,Deadline,Requested By,Description,URL,Owned By,Owned By,Blocker,Blocker Status,Comment,Comment,Task,Task Status,Task,Task Status,Task,Task Status,Task,Task Status,Task,Task Status
131983759,LAN API: GET /nowplaying should return track artwork,"",1,"Oct 24, 2016","Oct 30, 2016",feature,0,p3 - Low,accepted,"Oct 10, 2016","Oct 25, 2016",,Guillaume Khayat,"per zone",https://www.pivotaltracker.com/story/show/131983759,,,,,,,,,,,,,,,,
EOF
npm i @linear/import
npx linear-import
# input personal API key
# select Pivotal
# select test.csv fileExpected result
CSV gets imported in Linear
Actual results
HTTP400 error (Authentication required, not authenticated error)
Versions used
@linear/import: 1.9.9
node: v20.11.0
Thanks for filing this. We're unable to reproduce the 400 issue, and I have converted your sample data above into a CSV to import, tested on 2 workspaces (1 as admin, 1 as not) and both worked. Can you confirm you have inputted the correct personal API token? Maybe try to create a new one and paste it in?
(Don't worry, I have revoked the token above 😉)
Mmh.
I've generated & tried 3 different Personal API keys. I copy-paste them straight from the linear web app.
Here is my latest attempt (key is revoked too):
I'm admin of our workspace.
Anything I should do to get a better understanding of what's going on?
Ah well it works now.
The only thing I changed was I deleted all cache (indexedDB, cookies, etc) from my browser and regenerated a new personal key.
I don't understand what could have happened.
I'll close the ticket if the issue does not come back.
thanks, we will investigate the logs and see if we can come up with a more concrete answer here
also please make sure you revoke the key above (i'm sure you did, but due diligence…)